Required Workflows break repository auto_init #58854
Replies: 4 comments 1 reply
-
You need to create a new repo |
Beta Was this translation helpful? Give feedback.
-
I'm seeing this same issue. Unless I'm misunderstanding, this effectively prevents us from creating any new repos without temporarily disabling the required workflow. |
Beta Was this translation helpful? Give feedback.
-
It seems like Repository Rulset will replace the Required workflows |
Beta Was this translation helpful? Give feedback.
-
Was there any update to this after the move to repository rulesets? I'm having the same issue where a required workflow configured through a repository ruleset is breaking the auto_init of a new repository. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
When creating a new GitHub repository either via UI or API, we have the option to initialize the repo with a
README.md
file. This works perfectly fine until we introduce the Required Workflows in the organization. If the Required Workflows is enabled for all repositories, the newly created repository won't have any content, it will just be an empty repository. If you try to clone and push the first commit ever to the default (main
) branch, you will receive the following error:According to GitHub's blog post https://github.blog/changelog/2023-03-10-github-actions-required-workflows-improvements/.
This makes sense only for the repositories that already have the default branch pushed. For a new, empty repository, it shouldn't prevent us from initializing the default branch for the first time.
WDYT? I know that Required Workflows is still under Beta, any enhancement will be made soon?
Beta Was this translation helpful? Give feedback.
All reactions