Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .mergify.yml
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,9 @@ queue_rules:
- check-success = build
# Semi-linear history: rebase the PR onto main, then merge it with a merge commit
update_method: rebase
# GitHub only lets Mergify update a pull request created by another GitHub App
# (Renovate) by impersonating a user
update_bot_account: nafg

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep an account-free queue for fork pull requests

In this configuration, default is the only queue and its conditions also match ordinary contributor PRs once build succeeds; the Renovate author condition restricts only automatic enqueueing, while @mergifyio queue selects the first matching queue. With in-place checks and update_method: rebase, setting update_bot_account causes Mergify to reject PRs from forks, whereas previously it could rebase ordinary fork PRs through GitHub's API. The queue command documentation confirms manual routing, and the queue-rule documentation documents the fork rejection. Use a separate Renovate-specific queue with this account so maintainers can still queue external contributors' PRs.

Useful? React with 馃憤聽/ 馃憥.

merge_method: merge

pull_request_rules:
Expand Down
Loading