gh-issue-locking
Claim/lock/release protocol for GitHub issues worked by AI agents, with multi-operator coordination etiquette. Use whenever an orchestrator is about to claim, dispatch, or start work on an issue (lock BEFORE dispatch, always); whenever a PR linked to a claimed issue merges or closes (release the lock and explicitly close the issue — GitHub auto-close does not fire on non-default integration branches); whenever you find an issue carrying a lock label or lock comment and must decide active-vs-stale; and during any batch flow that claims multiple issues in one pass — even if the user only says "pick up the next issue", "work #N", "fix", "release the lock", or "why is this issue still open". Also covers bundled-issue locks, stale-lock reclaim, the multi-claim race re-check, and what to do when another operator already holds the lock.
Pinned to revision 6b9d66f636cc, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.