chore: sync GitHub repo metadata from rhiza v1.3.3 - #28
Conversation
The seven files here are the part of the v0.18.8 -> v1.3.3 template sync that no runtime depends on: issue/discussion templates, branch and tag rulesets, the dependabot config and the PR template. Nothing reads them at build or test time, so they carry none of the coupling that keeps the rest of the sync atomic — the workflow pins, the make.d plumbing and the .rhiza/tests layout all move in lockstep and stay in the larger PR. Split out so this part can merge on its own review. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 59 minutes Limit details: You’ve used all 1 included review currently available under your plan. 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 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 for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
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. Comment |
There was a problem hiding this comment.
Pull request overview
This PR syncs GitHub repository metadata files from the Rhiza template (v1.3.3), adding standard repo configuration/documentation and aligning templates/rulesets with upstream so maintenance and automation expectations are consistent.
Changes:
- Add GitHub ruleset JSON definitions for default-branch and version-tag protection.
- Add GitHub Discussion templates and a
.github/CONFIG.mddoc describing required/optional Actions secrets. - Update
dependabot.ymlformatting and extend the PR checklist.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
.github/CONFIG.md |
Adds documentation for Rhiza workflow secrets and setup. |
.github/DISCUSSION_TEMPLATE/help-wanted.yml |
Adds a “Help Wanted” discussion template. |
.github/DISCUSSION_TEMPLATE/ideas.yml |
Adds an “Idea” discussion template. |
.github/rulesets/main-branch-protection.json |
Adds a default-branch protection ruleset definition. |
.github/rulesets/tag-protection.json |
Adds a version tag protection ruleset definition. |
.github/dependabot.yml |
Minor formatting cleanup. |
.github/pull_request_template.md |
Updates PR checklist (including changelog and dependency check item). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "rules": [ | ||
| { "type": "creation" }, | ||
| { "type": "update" }, | ||
| { "type": "deletion" }, | ||
| { "type": "non_fast_forward" } | ||
| ], |
| - [ ] `CHANGELOG.md` entry added (or not needed for this change) | ||
| - [ ] Documentation updated if behaviour changed | ||
| - [ ] `make deptry` passes (no unused or missing dependencies) | ||
| - [ ] `make deps` passes (no unused or missing dependencies) |
|
Superseded by alihaskar#91 — these seven files are rhiza-managed repo metadata, so they belong in the parent repo rather than in this fork. Same branch, same commit, retargeted at |
The part of the jebel-quant/rhiza
v0.18.8→v1.3.3sync that nothing at build or test time reads, split out of #27 so it can merge on its own review.Files (7)
.github/CONFIG.md.github/DISCUSSION_TEMPLATE/help-wanted.yml.github/DISCUSSION_TEMPLATE/ideas.yml.github/rulesets/main-branch-protection.json.github/rulesets/tag-protection.json.github/dependabot.yml.github/pull_request_template.mdWhy these and nothing else
The remaining 72 files of the sync are coupled and stay together in #27:
rhiza_*.ymlworkflow is a thin caller pinned at@v1.3.3, and those reusable workflows run against this repo's.rhiza/plumbing;quality.mk'srhiza-testprovisions dependencies for the flat.rhiza/testslayout, andpython.mkreads.rhiza/tests/test_pyproject.py;pytest.iniaddspythonpath = .rhiza/tests, and the deleted.rhiza/requirements/*.txtwere what the oldbootstrap.mkinstalled from.Land either order — there is no dependency between this PR and #27.
Note
.rhiza/template.locklives in #27 and lists these seven files as template-owned, so/rhiza:statuswill report drift on them until both PRs have merged.No gates were run — run
/rhiza:qualityfor a scorecard.