Skip to content

Commit 2c73cf3

Browse files
steveyeggeclaude
andcommitted
crew.md.tmpl: policy-aware PR guidance (check remote origin)
Makes PR rules conditional on repo ownership instead of absolute ban. Non-maintainer repos may require PRs for external contributors. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent 0b90837 commit 2c73cf3

1 file changed

Lines changed: 7 additions & 18 deletions

File tree

internal/templates/roles/crew.md.tmpl

Lines changed: 7 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -224,26 +224,15 @@ instructions immediately. Useful for one-off tasks that don't warrant a full bea
224224

225225
**Crew workers push directly to main. No feature branches.**
226226

227-
### ABSOLUTELY FORBIDDEN: Pull Requests
227+
### No PRs in Maintainer Repos
228228

229-
**NEVER create pull requests. This is not negotiable.**
229+
If the remote origin is `steveyegge/beads` or `steveyegge/gastown`:
230+
- **NEVER create GitHub PRs** - you have direct push access
231+
- Crew workers: push directly to main
232+
- Polecats: use `gt done` → Refinery merges to main
230233

231-
We are the sole maintainer. You have direct push access. The correct workflow is:
232-
1. Make changes
233-
2. Run tests
234-
3. Commit directly to main
235-
4. Push
236-
237-
**If you find yourself about to run `gh pr create` — STOP. You are doing it wrong.**
238-
239-
PRs are for *external contributors* submitting to repos they don't own. We own these
240-
repos. We don't review our own code via PR. We just push.
241-
242-
The "PR Sheriff" role (if you have it) reviews *incoming* PRs from *contributors*.
243-
It does NOT mean you create PRs yourself.
244-
245-
Check `git remote -v` if unsure — if it shows `steveyegge/beads` or `steveyegge/gastown`,
246-
you push directly. No PRs. Ever.
234+
PRs are for external contributors submitting to repos they don't own.
235+
Check `git remote -v` if unsure about repo ownership.
247236

248237
### The Landing Rule
249238

0 commit comments

Comments
 (0)