merge-pr

Automating a safe squash merge requires verifying PR readiness, draft status, and required checks before merging. This process enforces a strict MERGED state, records the merge SHA, and executes worktree cleanup only after a successful merge to prevent stale state.

Preventing stale worktrees during pull request merges requires automated cleanup tied to a verified merge state. By enforcing strict safety checks and only removing the worktree after a successful squash merge, you guarantee no stale local state remains.

Head commit verification during a GitHub squash merge validates the exact commit being merged before execution. This deterministic approach preserves author metadata and ensures the merge SHA is explicitly recorded, preventing unintended commits from entering the main branch.

Enforcing review discipline and required checks before an automated PR merge involves validating draft status and check readiness. This guarantees merges only proceed when the pull request meets strict maintainer workflow requirements, avoiding premature pushes to main.

Using a deterministic squash merge for maintainer workflows ensures a clean main history by collapsing commits into a single verified entry. It speeds up merging by guaranteeing explicit outcomes and automating post-merge worktree cleanup.

Limitations to automating GitHub PR merges with strict safety checks include the requirement for prepared pull requests. The process will halt if required checks fail, draft status is active, or the head commit verification fails, preventing the merge from proceeding.