AutoApproving Gitlab MR fails after rebasing branch #31833
Unanswered
bedaka
asked this question in
Request Help
Replies: 1 comment 1 reply
-
This is really a GitLab bug, not Renovate. Can you experiment locally (running Renovate from source) too see how long it takes for GitLab to allow reapprovals? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab SaaS, Renovate 38.110.2
Please tell us more about your question or problem
Hello,
we experience the issue that we cannot merge Merge Requests (MRs) created by Renovate after they were rebased due to updates because of missing approvals. Investigation of the logs shows that Renovate in fact fails to re-approve the MR because it tries to approve faster than GitLab is removing the approval from the MR. This seems to be the same issue like #30557 .
Timeline:
This requires us to rebase the branch again, which will succeed because the MR is not approved yet.
Our configuration:
Thank you so much,
bedaka
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions