docs(contributing): harvest-credit close template + stewardship branch explanation#2986
docs(contributing): harvest-credit close template + stewardship branch explanation#2986Hmbown wants to merge 1 commit into
Conversation
…h explanation Encodes two process decisions from the 2026-06-09 triage: - harvested PRs are closed with a comment naming the contributor, the landed commits/PRs, and a tracking issue for any remainder (the #2634 pattern, now the template) - documents codex/v0.9.0-stewardship's role so external contributors base layered refactor series correctly (as #2888 already does) Refs #2985. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the CONTRIBUTING.md file to document the template for closing harvested PRs by hand and introduces the "Stewardship Branch" workflow for staging large refactors. The review feedback suggests replacing the hardcoded version v0.9.0 in the branch name with a generic placeholder (e.g., codex/v<version>-stewardship) to prevent the documentation from quickly becoming outdated.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| Large refactors and architecture work stage on | ||
| `codex/v0.9.0-stewardship` before reaching `main`. The branch exists so |
There was a problem hiding this comment.
Hardcoding the specific version v0.9.0 in the branch name will cause this documentation to quickly become outdated as the project progresses. Consider using a placeholder like codex/v<version>-stewardship to keep the guide maintainable across future releases.
| Large refactors and architecture work stage on | |
| `codex/v0.9.0-stewardship` before reaching `main`. The branch exists so | |
| Large refactors and architecture work stage on | |
| `codex/v<version>-stewardship` (e.g., `codex/v0.9.0-stewardship`) before reaching `main`. The branch exists so |
|
|
||
| What this means for you: | ||
|
|
||
| - **Base layered/EPIC-sized refactor PRs on `codex/v0.9.0-stewardship`** |
There was a problem hiding this comment.
Use the placeholder version here as well to maintain consistency with the section introduction.
| - **Base layered/EPIC-sized refactor PRs on `codex/v0.9.0-stewardship`** | |
| - **Base layered/EPIC-sized refactor PRs on `codex/v<version>-stewardship`** |
1 participant
Two process additions from the 2026-06-09 triage session, for owner review:
codex/v0.9.0-stewardship's role so external contributors base layered refactor series correctly (as @aboimpinto already does with refactor(commands): extract registry and parser helpers #2888).Refs #2985 (release-flow hygiene, filed separately).
🤖 Generated with Claude Code