[PR #6369/13b6b4dd backport][3.8] Fix setting branch protection failure in GHA #6370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
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)
5 tasks
webknjaz
deleted the
patchback/backports/3.8/13b6b4dde8c29074fed185900d168a27e9eb7c28/pr-6369
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #6369 as merged into master (13b6b4d).
What do these changes do?
This is necessary to resolve the problem of GitHub treating the
skippedcheckjob 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.txtCHANGESfolder<issue_id>.<type>for example (588.bugfix)issue_idchange 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.