ad-merge

Automate GitHub PR merges by evaluating CI status and review outcomes using gh CLI, then applying an auto-detected merge strategy. The workflow performs preflight checks to ensure CI passes and approvals exist before safely executing the merge.

Yes, you can delete a branch after a GitHub pull request merge by executing the gh pr merge command with the --delete-branch flag. This ensures feature branches are cleaned up automatically once the merge is successfully completed.

The auto-detected merge strategy selects between squash, rebase, or merge commits based on the PR context. It evaluates the pull request status via gh api to determine the most appropriate method for landing the changes.

To evaluate a GitHub PR before merging, you need the gh CLI to satisfy preflight checks and retrieve PR status. The evaluation checks CI results, review approvals, and detects linked tasks or ADR references to ensure it is mergeable.

Yes, this PR merge automation works without additional dependencies because it relies entirely on the gh CLI. It uses gh pr and gh api commands to retrieve status, evaluate checks, and execute the merge directly.

You should not use automated GitHub PR merging when a pull request requires manual intervention, has failing CI checks, or lacks the necessary review approvals. The workflow enforces these gates and will not merge if preflight conditions are unmet.