mergify-merge-protections

You can block a GitHub pull request from merging until dependent PRs land by adding a Depends-On header to the PR body, which enforces cross-repo or same-repo dependency rules. This coordinates multi-repo feature launches or schema migrations.

Yes, you can schedule a GitHub pull request to merge at a specific date and time by adding a Merge-After header to the PR body. This is useful for coordinating embargoed releases or timed feature launches.

A scheduled merge freeze is a repository-wide or conditional halt on all pull request merges. You need it during deployment windows, incident response, or code freeze periods to prevent breaking changes from merging into production.

Yes, Mergify supports merge freeze exclusions for hotfixes using conditional matching and exclusion rules. You can apply labels like hotfix to allow specific pull requests to bypass the freeze and merge during incidents.

You coordinate cross-repo pull request merges by using Depends-On headers in the PR body to specify required dependent PRs across repositories. This blocks merging until all required changes land successfully.

The best way to halt all PR merges during an incident response is to create a scheduled merge freeze with conditional matching rules. This stops all pull requests from merging while allowing hotfix exclusions if needed.