.png%3Falt%3Dmedia%26token%3D0abeb39f-a80f-4705-90e6-247dd98e5ab9)
.png%3Falt%3Dmedia%26token%3D0abeb39f-a80f-4705-90e6-247dd98e5ab9)
Comment on page
MergeQueue
There could be several reasons why the bot is not merging your PR.
- Check your Dashboard to see whether the queue is active or paused. If the queue is paused it will not pick up any changes.
- Check if all your CI statuses are completed (no required status is still pending).
- Check if there is no other PR ahead of your PR that is pending merge.
- Go to the GitHub app page and verify that the app is still authorized to your repository. If not, you may need to reconnect the app.
Once you have verified the above status, open your web app, and look at the Open and Blocked Queue. If your PR is in the Blocked Queue, there should be a reason listed for blocking as well. If none of these steps help, please contact us [email protected]
When a repository is configured to require commits to be signed, all commits in PRs must be signed with the committer's GPG key. MergeQueue will not merge PRs that contain unsigned commits if this option is enabled. If your commits are signed, but you're still facing this error, make sure that you've uploaded your GPG public key to GitHub.
To learn more about signing commits, see GitHub's "Signing commits" documentation. If you need to sign commits that already exist, you'll need to interactively rebase your PR and sign the commits individually (
git rebase -i HEAD~N for the relevant value of N, and, for every commit, add exec git commit --amend --no-edit --no-verify --gpg-sign below every pick ... line). You'll need to force push the branch or open a new pull request after doing this.Last modified 7mo ago