mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-18 18:32:28 +08:00
Merge remote-tracking branch 'origin/main' into garrytan/codex-compat-wave2
# Conflicts: # .agents/skills/gstack-autoplan/SKILL.md # .agents/skills/gstack-benchmark/SKILL.md # .agents/skills/gstack-browse/SKILL.md # .agents/skills/gstack-canary/SKILL.md # .agents/skills/gstack-design-consultation/SKILL.md # .agents/skills/gstack-design-review/SKILL.md # .agents/skills/gstack-document-release/SKILL.md # .agents/skills/gstack-investigate/SKILL.md # .agents/skills/gstack-land-and-deploy/SKILL.md # .agents/skills/gstack-office-hours/SKILL.md # .agents/skills/gstack-plan-ceo-review/SKILL.md # .agents/skills/gstack-plan-design-review/SKILL.md # .agents/skills/gstack-plan-eng-review/SKILL.md # .agents/skills/gstack-qa-only/SKILL.md # .agents/skills/gstack-qa/SKILL.md # .agents/skills/gstack-retro/SKILL.md # .agents/skills/gstack-review/SKILL.md # .agents/skills/gstack-setup-browser-cookies/SKILL.md # .agents/skills/gstack-setup-deploy/SKILL.md # .agents/skills/gstack-ship/SKILL.md # .agents/skills/gstack/SKILL.md # .github/workflows/skill-docs.yml # README.md
This commit is contained in:
@@ -56,7 +56,7 @@ project where you actually felt the pain.
|
||||
|
||||
### Session awareness
|
||||
|
||||
When you have 3+ gstack sessions open simultaneously, every question tells you which project, which branch, and what's happening. No more staring at a question thinking "wait, which window is this?" The format is consistent across all 15 skills.
|
||||
When you have 3+ gstack sessions open simultaneously, every question tells you which project, which branch, and what's happening. No more staring at a question thinking "wait, which window is this?" The format is consistent across all skills.
|
||||
|
||||
## Working on gstack inside the gstack repo
|
||||
|
||||
@@ -342,6 +342,23 @@ bun install && 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
|
||||
|
||||
When you're happy with your skill edits:
|
||||
|
||||
Reference in New Issue
Block a user