`wait-for-build` merges without all checks completed
See original GitHub issuePlease ensure:
- The bug is caused by Refined GitHub. It doesn’t happen if I disable the extension.
Include in this issue:
- Screenshots/video/gif demonstrating the bug, if it’s visual
- Console errors, if any
Description
I checked the Wait for successful checks
checkbox, pressed the merge button and switched to another tab and window. When i switched back to the PR tab, i noticed that the PR was already merged without all of the checks completed
Console output
Example URL
https://github.com/Terrania/Baystation12/pull/29
Browser(s) used
Yandex.Browser
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
`wait-for-build` currently broken · Issue #1792 · refined-github ...
"Wait for successful checks" isn't waiting ... all I saw is that the merge went through without waiting even if the checkbox was...
Read more >Allow developers to merge into a protected branch without ...
When the checkbox is enabled, a developer can merge MRs into that protected branch from the Web UI and from the command-line (any...
Read more >Auto-complete fails due to requested merge-type *changing ...
Have a repository with a limited list of permitted merge types (at least not no-ff): Branch policy: Create a PR such that any...
Read more >More reliable merge checks - Bitbucket
We're excited to announce more reliable merge checks. ... Once all builds have completed, the new validation checkmark will be checked.
Read more >Checks for merging pull requests | Bitbucket Data Center and ...
Merge checks stop pull requests from being merged until they meet ... No incomplete tasks - requires all tasks to be complete before...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it may be time to retire the feature or switch to using the API instead, we can’t risk it go through like this.
GitHub’s new merge queue feature might be a good replacement for the feature
Sorry, I didn’t notice the “2 of 5 checks passed”. From your workflow file, I suppose it’s the “Maps” check (which has a
matrix
of 3) hadn’t passed yet whenwait-for-build
merged the PR.Implementation-wise the feature just look at GitHub’s check icon, if GitHub shows the checks as passing, the we assume the checks have passed. The real problem could be what @yakov116 has described.