-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automerge on hold reason #6311
Comments
On removal of 'branch protection rules' from our master branch, automerges continued, which confirmed this issue for me. |
We can probably cover a few of these reasons but not all branch protection rules may be easily visible to us at the API level unfortunately. I saw a case today where all status checks returned "success" yet |
Needs some exploration of the GitHub API to determine which of the failure conditions we can determine and from which queries. |
Maybe an idea: try automerge PR's as usual, if failed, check protection rules for possible causes. 🤔 |
Good idea. If it takes any extra queries to determine then we should do it lazily and once per repo, as rules are common per-repo and not per-PR. |
Duplicate of #2702 |
What would you like Renovate to be able to do?
If automerge is enabled, I’d like to be given the reason why the pull request isn’t being merged.
Describe the solution you'd like
In the body of the pull requests, beside the automerge enabled indicator, the reason renovate is not currently merging the PR should be displayed.
Describe alternatives you've considered
Manually merging pull requests which are passing status checks and are fully rebased, due to not being aware of the reason for no automerge taking place.
Additional context
Several branch permissions can be configured, any of which could be preventing an automerge, there may be other situations outside of branch permissions which could also correspond to this state.
The text was updated successfully, but these errors were encountered: