Allow "Require status checks to pass" to allow no checks and to included dynamic checks added to Pull Requests in its calculation #130674
Replies: 2 comments
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
There are so many open issues related to this, as well as community solutions that almost manage to support it. All because what seems like the mindblowingly obvious setting (require all checks that are triggered by the pr but only those triggered by the pr to pass) is not available in github. Fyi https://github.com/upsidr/merge-gatekeeper is a community solution that allows you to only specify itself as a required check and it will check if any of the triggered checks fail. You can explicitly specify checks that you don't need to pass. The only problem, that we recently encountered, is that it doesn't seem to be aware of queued workflows that haven't yet started. So if at any point there are queued workflows but no running workflows, it will pass. This is normally not a concern, but we run our workflows in AWS spot instances that might not be available, so workflows might queues for a while. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm working on migrating our organization's repositories from ADO to GitHub. Our CI/CD pipelines will continue to live in ADO. I'm looking to avoid having to set up branch policies for every repository and so far have been partially successful by adding Azure Pipelines pr definition to the pipeline yaml files. Doing this allows automatic pipeline execution validation on PR creation as well as automatically adds status checks to the GitHub PR itself. This is GREAT! BUT, I also want to require that the status checks are passing before allowing for the PR to complete. Currently if I select "Require status checks to pass before merging" it requires me to select status checks - this is painful as the pipelines are in ADO and the search is not great as well as potentially having duplicate pipeline names across multiple projects, as well as burdensome with 200+ repositories.
Is there a way that I can assert or require all status checks that are on a PR to pass without explicitly defining them as a branch policy /branch ruleset item?
Beta Was this translation helpful? Give feedback.
All reactions