Skip to content
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

Recent GitHub change breaks required workflows / branch protection rules #825

Open
MarvinJWendt opened this issue Oct 31, 2023 · 2 comments
Labels

Comments

@MarvinJWendt
Copy link

MarvinJWendt commented Oct 31, 2023

Recently, GitHub announced to deprecate the old way of handling required workflows:

Starting September 20th, 2023, users can configure their workflows using rulesets in order to run and pass in selected repositories before merging their code. On October 18th, users will no longer be able to access Actions Required Workflows and must use rulesets in its place.

This means, that since October 18th, required workflows are no longer working as expected.

/cc @travi

Related to: #625

@travi
Copy link
Member

travi commented Nov 3, 2023

i dont understand what you are trying to highlight with this. required workflows was a feature that was independent of branch protection rules and no specific support for them has been added to the settings app, so i dont understand the impact you are highlighting from that announcement

@MarvinJWendt
Copy link
Author

Sorry, maybe I misunderstood something in the blog post, all I saw was that my new repository did not apply the branch protection rules correctly (required Actions on PRs were not set). I figured it might have been this change, but yeah, maybe it's unrelated to the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants