Skip to content

ci(mergify): remove the delete_head_branch action - #6319

Open
mergify[bot] wants to merge 1 commit into
mainfrom
mergify/configuration-deprecated-update/delete_head_branch_action_removal
Open

mergify[bot] wants to merge 1 commit into
mainfrom
mergify/configuration-deprecated-update/delete_head_branch_action_removal

ci(mergify): remove the `delete_head_branch` action

be752d4
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 20, 2026 in 2s

1 rule matches and 2 potential rules

The delete_head_branch action is deprecated, and Mergify can stop accepting it at any time from 2026-07-31. Turn on GitHub's 'Automatically delete head branches' setting (https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches), then remove the action from your configuration. GitHub's setting deletes the head branch of a merged pull request only.

Rule: delete the head branch after merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • merged

Rule: ask to resolve conflict (comment)

  • conflict

✅ Rule: remove outdated reviews (dismiss_reviews)

  • base=main

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: approve automated PRs that have passed checks (label, review)

  • author=cloudpossebot
  • head~=auto-update/.*
  • any of:
    • check-skipped~=.*package.*
    • check-success~=.*package.*
  • any of:
    • check-skipped~=.*alpine.*
    • check-success~=.*alpine.*
  • #check-pending=0
  • #files<=6
  • -check-failure~=.*alpine.*
  • -check-failure~=.*matrix.*
  • -check-failure~=.*package.*
  • base=main
  • check-success~=.*build-and-push.*

Rule: merge automated PRs when approved and tests pass (merge)

  • #approved-reviews-by>=1
  • author=cloudpossebot
  • github-review-approved [🛡 GitHub branch protection]
  • head~=auto-update/.*
  • any of:
    • check-skipped~=.*package.*
    • check-success~=.*package.*
  • any of:
    • check-skipped~=.*alpine.*
    • check-success~=.*alpine.*
  • #changes-requested-reviews-by=0
  • #check-pending=0
  • #commented-reviews-by=0
  • -check-failure~=.*alpine.*
  • -check-failure~=.*matrix.*
  • -check-failure~=.*package.*
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • base=main
  • check-success~=.*build-and-push.*
  • any of: [📌 merge -> configuration change requirements]
    • check-success = @mergify/Configuration changed
    • -mergify-configuration-changed
    • check-success = @mergify/Configuration has been deleted
  • any of: [🛡 GitHub branch protection]
    • check-success = build-and-push
    • check-neutral = build-and-push
    • check-skipped = build-and-push
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com