-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 can happen after a force-push without waiting for tests #3099
Comments
What do the logs show for the run where that happened? We normally should log the result of the commit status checks. |
Also, if you need to enforce that Travis tests pass before merging, you can add that as part of branch protection for |
I missed the exact log link you gave originally. Copy/pasting from that run:
|
Added an extra branch status check to check for this edge case where we're pushing to a PR that had previously passed tests. Thanks @abraham |
🎉 This issue has been resolved in version 13.179.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Awesome! Thanks. |
What Renovate type are you using?
Renovate GitHub App
Describe the bug
V8.0.0 of ts-node was released an update PR was opened, and the tests pass. v8.0.1 of ts-node is released and the PR is force-pushed with the new version, the PR is immediately merged without waiting for a new CI run.
Did you see anything helpful in debug logs?
Based on 40758419 it looks like the PR was updated and merged in the same job.
To Reproduce
Get an update PR, have CI succeed, find new update for same package.
Expected behavior
I would expect force-pushing a PR to wait until CI runs succeed to merge.
Screenshots
This is a screenshot of the PR just after the PR was merged showing pending checks:
Additional context
This seems to have happened on a half-dozen or so of my repos.
The text was updated successfully, but these errors were encountered: