CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-08 06:26:45 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: add community PR triage process to CONTRIBUTING.md

Browse Source 
Document the wave-based PR triage pattern used for batching community
contributions. References PR #205 (v0.8.3) as the original example.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-22 09:57:45 -07:00
parent 03a8904afa
commit 5daba1c6e6
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+17
View File
@@ -342,6 +342,23 @@ bun install && bun run build
This affects all projects. To revert: `git checkout main && git pull && bun run build`. This affects all projects. To revert: `git checkout main && git pull && bun run build`.
## Community PR triage (wave process)
When community PRs accumulate, batch them into themed waves:
1. **Categorize** — group by theme (security, features, infra, docs)
2. **Deduplicate** — if two PRs fix the same thing, pick the one that
changes fewer lines. Close the other with a note pointing to the winner.
3. **Collector branch** — create `pr-wave-N`, merge clean PRs, resolve
conflicts for dirty ones, verify with `bun test && bun run build`
4. **Close with context** — every closed PR gets a comment explaining
why and what (if anything) supersedes it. Contributors did real work;
respect that with clear communication.
5. **Ship as one PR** — single PR to main with all attributions preserved
in merge commits. Include a summary table of what merged and what closed.
See [PR #205](../../pull/205) (v0.8.3) for the first wave as an example.
## Shipping your changes ## Shipping your changes
When you're happy with your skill edits: When you're happy with your skill edits: