Repository navigation
Set a Mergify update_bot_account so Renovate PRs can be queued - #304
Conversation
Mergify refused to queue #266: "This pull request was created by another GitHub App. You must set up an update_bot_account on your queue_rules to automatically queue and merge PRs created by a GitHub App." Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 780bb0039a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 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 |
There was a problem hiding this comment.
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 👍 / 👎.
1 participant
Mergify refused to queue #266 under the config from #303:
This sets
update_bot_account: nafgon thedefaultqueue. Mergify will rebase Renovate PRs in place as that user (shown as force-pushes bynafg). Per the queue rules docs, the account must have logged into the Mergify dashboard at least once and have write/maintain/admin permission.After merge,
@Mergifyio refreshon #266 should re-queue it, which is the first real test of the in-place rebase + merge commit flow.🤖 Generated with Claude Code