Skip to main content

polecat

PR-Flow Polecat Policy​

Rig Policy — overrides formula instructions where they conflict.

This rig uses a polecat → GitHub PR → human review flow. After pushing your branch, you MUST ensure a GitHub PR is open for it before running gt done.

This overrides the canonical Refinery merge-queue assumption embedded in mol-polecat-work. gt done is still the completion signal — but in this rig, a visible PR is the gating artifact for review.

Required steps after implementation​

  1. Push the branch explicitly (do not rely on gt done to push): 
    git push -u origin HEAD
  2. Check whether a PR already exists for the branch: 
    gh pr view "$(git branch --show-current)" >/dev/null 2>&1
  3. If no PR exists, create one against the base branch: 
    gh pr create --fill --base main
  4. Only then run gt done.

Do NOT​

  • Run gt done without a PR open — the review loop breaks.
  • Merge your own PR. A maintainer or the merge queue handles merging.
  • Push directly to main.

If gh commands fail​

Auth, rate-limit, missing PR template, or unknown base branch — do NOT skip PR creation to unblock yourself. Escalate to your Witness:

gt mail send <rig>/witness -s "HELP: gh pr create failed" -m "Branch: $(git branch --show-current)
Error: <paste>
Tried: <what you attempted>"