chore: drop redundant .rhiza/.env and .rhiza/.gitignore

[tschm]

Removes two .rhiza/ files that no longer carry any configuration.

.rhiza/.env

Its only two assignments were:

MARIMO_FOLDER=docs/notebooks
SOURCE_FOLDER=src

Both are byte-identical to the ?= defaults in .rhiza/rhiza.mk:103-106. Since rhiza.mk:94 pulls the file in with -include, its absence is a no-op — the defaults apply unchanged.

Dropping it also restores the env-overridability the file's own header describes: a makefile assignment beats an exported environment variable in GNU make's precedence order, so pinning these two here made them command-line-only overrides for no benefit.

.rhiza/.gitignore

Contained a single rule, !.env, which existed solely to un-ignore .rhiza/.env against the root .gitignore:11. With the .env gone it has nothing to un-ignore.

Verification

make doctor runs clean after the removal; pre-commit passes.

Note

Both files are template-owned and synced by rhiza. Unless upstream drops them too, a future /rhiza:update may restore them.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@tschm, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1c5aaa52-8588-4555-9914-541834b9d9f9

📥 Commits

Reviewing files that changed from the base of the PR and between c37efa4 and 61795e8.

📒 Files selected for processing (2)

• .rhiza/.env
• .rhiza/.gitignore

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR removes two redundant .rhiza/ files whose contents are already covered by defaults in .rhiza/rhiza.mk, simplifying the repo’s Rhiza template footprint without changing behavior.

Changes:

• Delete .rhiza/.env, relying on .rhiza/rhiza.mk defaults for SOURCE_FOLDER and MARIMO_FOLDER via ?= assignments and -include.
• Delete .rhiza/.gitignore, which previously existed only to un-ignore the now-removed .rhiza/.env.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.rhiza/.env	Removed redundant env overrides now covered by rhiza.mk defaults.
.rhiza/.gitignore	Removed un-ignore rule that only supported tracking .rhiza/.env.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.