github-operations

To prevent mutating the wrong GitHub issue or PR, you must capture the exact canonical number printed in the gh create command output and validate that number before performing any subsequent mutations like comments, edits, or labeling.

You need to validate a GitHub issue number before editing or commenting whenever you create an issue or PR with gh and then perform subsequent mutations. Guarding these mutational actions requires using the exact number from the creation output in the same turn.

To safely close or label a GitHub PR created with gh CLI, enforce capturing and validating the canonical URL printed by gh pr create. You must use that exact validated number before executing any subsequent mutational actions such as closing or labeling.

GitHub issue and PR number tracking causes cross-entity mutation mistakes because issues and PRs share a single counter. Treating them as sharing one numbering sequence and validating the canonical URL prevents targeting the wrong entity during mutations.

Yes, the mutation safety approach works with both gh issues and gh prs commands. It applies whenever creating issues or PRs with gh and performing subsequent mutations such as comments, edits, closes, or labeling using the validated number across both entity types.