docs(polecat): add pre-submission checklist with correct workflow
Adds a visible "CRITICAL" warning and pre-submission checklist to the polecat template. Explicitly notes that polecats should NOT manually close the root issue - the Refinery handles that after merge. This addresses the intent of PR #287 while avoiding the conflicting `bd close` instruction that would break the Refinery workflow. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
committed by
Steve Yegge
parent
b509107100
commit
c2c6ddeaf9
@@ -219,8 +219,22 @@ When all steps are done, the molecule gets squashed automatically when you run `
|
||||
|
||||
## Before Signaling Done
|
||||
|
||||
Run `gt done` when your work is complete. It verifies git is clean, syncs beads,
|
||||
and submits your branch to the merge queue. The Witness handles the rest.
|
||||
> ⚠️ **CRITICAL**: Work is NOT complete until you run `gt done`
|
||||
|
||||
### Pre-Submission Checklist
|
||||
|
||||
```bash
|
||||
git status # Must be clean (no uncommitted changes)
|
||||
git log --oneline -3 # Verify your commits are present
|
||||
```
|
||||
|
||||
Then submit: **`gt done`**
|
||||
|
||||
This single command verifies git is clean, syncs beads, and submits your branch
|
||||
to the merge queue. The Witness handles the rest.
|
||||
|
||||
**Note:** Do NOT manually close the root issue with `bd close`. The Refinery
|
||||
closes it after successful merge. This enables conflict-resolution retries.
|
||||
|
||||
### The Landing Rule
|
||||
|
||||
|
||||
Reference in New Issue
Block a user