-
Notifications
You must be signed in to change notification settings - Fork 45
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
Bug: does not observe required checks #73
Comments
@hfaulds Some folks might actually want all checks rather than just the required ones. How would you feel about a new input parameter like: checks: all
and: checks: required
Depending on which input param is used, that determines which graphql query we make to determine if we are 🟢 or not for the deploy. Thoughts? |
@GrantBirki introducing |
👋 Hey folks! I have good news. We had an excellent open source contribution to this project that has implemented the All details about this new input option can be found in the following release -> Since it has been quite a while since this issue was first opened, I will go ahead and ping (@ mention) a few people that seemed interested in this feature. @hfaulds @tiagonbotelho @metaory @KevinMSampson @pauleustice @redoz @bzurkowski Cheers! 🎉 |
At the moment deploys are blocked on all status checks passing, even if they're not required.
This is because
statusCheckRollup.state
doesn't care about whether a check is required or not:https://github.com/github/branch-deploy/blob/43afd75c657a06c55c953cc7af493d9cf565aa43/src/functions/prechecks.js#LL151
I don't know if there's an elegant way to check this 😢 (especially one that avoids paging through results). The best graphql I could come up with was this:
The text was updated successfully, but these errors were encountered: