-
-
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
Fix setting branch protection failure in GHA #6369
Conversation
This is necessary to resolve the problem of GitHub treating the `skipped` `check` job result as an acceptable outcome and merging broken Dependabot PRs with auto-merge. For example: aio-libs#6330. Inspired by: pyca/cryptography#6512 (comment)
@Dreamsorcerer you're going to like this. |
Codecov Report
@@ Coverage Diff @@
## master #6369 +/- ##
=======================================
Coverage 93.32% 93.32%
=======================================
Files 103 103
Lines 30377 30377
Branches 3058 3058
=======================================
Hits 28350 28350
Misses 1850 1850
Partials 177 177
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Backport to 3.8: 💚 backport PR created✅ Backport PR branch: Backported as #6370 🤖 @patchback |
This is necessary to resolve the problem of GitHub treating the `skipped` `check` job result as an acceptable outcome and merging broken Dependabot PRs with auto-merge. For example: #6330. Inspired by: pyca/cryptography#6512 (comment) PR #6369 (cherry picked from commit 13b6b4d)
Backport to 3.9: 💚 backport PR created✅ Backport PR branch: Backported as #6371 🤖 @patchback |
This is necessary to resolve the problem of GitHub treating the `skipped` `check` job result as an acceptable outcome and merging broken Dependabot PRs with auto-merge. For example: #6330. Inspired by: pyca/cryptography#6512 (comment) PR #6369 (cherry picked from commit 13b6b4d)
…re in GHA (#6370) Co-authored-by: Sviatoslav Sydorenko <[email protected]>
This is necessary to resolve the problem of GitHub treating the `skipped` `check` job result as an acceptable outcome and merging broken Dependabot PRs with auto-merge. For example: #6330. Inspired by: pyca/cryptography#6512 (comment) PR #6369 (cherry picked from commit 13b6b4d) Co-authored-by: Sviatoslav Sydorenko <[email protected]>
What do these changes do?
This is necessary to resolve the problem of GitHub treating the
skipped
check
job result as an acceptable outcome and mergingbroken Dependabot PRs with auto-merge. For example:
#6330.
Inspired by:
pyca/cryptography#6512 (comment)
Are there changes in behavior for the user?
No, only for the maintainers.
Related issue number
#6330 (among others)
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.