Ignoring specific checks for automerge #29147
Replies: 1 comment
-
Your configuration sounds good to me. 😉 Quote from Renovate docs, Note If you use the default This means you should:
And a optional step: enable GitHub Merge Queue to speed up automerges, read the Renovate docs, key concepts automerge, GitHub Merge Queue to learn more. |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
Some of my projects have nondeterministic tests that can cause the measured code coverage to vary slightly on separate runs, even on PRs that don't touch the code (such as Renovate's dependency-bumping PRs). This means that a Renovate PR could end up with one or two failing Codecov checks, yet I do not want such failures to prevent automerging; on the other hand, I do want failures of the actual GitHub Actions tests to prevent automerging. How can I achieve this result?
Based on my reading of Renovate's documentation, I suspect that the following setup should work:
automerge
totrue
platformAutomerge
attrue
Unfortunately, when I tried to test this setup out, the coverage checks kept passing over & over, so I was not able to observe what happens when they fail on a Renovate PR. Rather than risking finding out the hard way that this setup doesn't work several months from now, I thought I'd ask for confirmation from the Renovate experts.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions