Workflow isn't enabled in repos generated from template


N.B. This issue appeared today morning. I had working flow for more than a week.

The issue:
I have a template repository with working workflow in my organization. When I create new repo from this template, workflows aren’t enabled automatically.

In Actions section I can see broken stylings:

After page reload stylings become even more broken, footer disappears and central div goes to the left.
Both repository and organization settings have Allow all actions tick.

Does anyone now what happened?
Is this behavior expected?
Is there fix or workaround?



We also have a similar use-case that just recently quit working. We create a new Repo via API using a repository template. The template repo contains a workflow. In our case, we typically create the new Repo in a 2nd organization, which can be done using the API.

I do not believe there is any API that can enable the disabled workflows, for the case Workflows aren't being run on this repository.

Note that I understand the reason for disabling workflows for a forked Repo.

I’m having the same problem, using GitHub Classroom which makes heavy use of template repositories. All of my students are finding that their tests are now not running, unless they enable actions manually as in the above instructions.

@vromash, @munderseth, @dmusican,

Sometimes, when creating a new repository, you need to manually enable the Actions on the repository via clicking the “Enable Actions on this repository” button. Most of time, this situation occurs when you fork a repository and creating a new repository from template.

Both repository and organization settings have Allow all actions tick.

This option is not related this question. The options “Allow all actions”, “Allow local actions only” and “Allow select actions” are used to set which actions are allowed to be used in the workflows within current organization or repository.

  • Allow all actions - - actions from anywhere are allowed to be used in the workflows within current organization or repository.

  • Allow local actions only - - actions only defined in the repositories within current organization are allowed to be used in the workflows within current organization or repository.

  • Allow select actions - - actions only match the specified criteria are allowed to be used in the workflows within current organization or repository.

To view more details, you can see “Disabling or limiting GitHub Actions for your organization”.

@brightran, before that issue was reported, enabling Actions was not required at all for the Template Repositories at all.

I have created and maintain IntelliJ Platform Plugin Template project that is supposed to run the Template Cleanup workflow when the user clicks Use this template button - i.e., to set the plugin project name to match the current repository name, cleanup README, etc.
In general, it’s a part of the workflow that is required to make everything working.

For now, there are over 400 projects created from that template with that workflow successfully triggered.

I find the current behavior as a bug and requiring users to enable Actions and pushing a commit to the remote repository breaks the whole concept of that template.

Is there anything we can do about that?

1 Like

@brightran Can you clarify what you mean by “sometimes”? Again, this is a change in behavior from what it was just a couple of days ago. This is affecting teachers who use GitHub Classroom in a way it didn’t just two days ago, and makes the experience for students more difficult.


As mentioned above, workflows were enabling automatically at the start of the week. Our project is built around actions and repo generating from template. While it’s not working we can’t continue development.

It would be great if the old functionality could be returned back or created endpoint which allowed us to enable workflows.

1 Like

When you click on the Actions tab do you see a button to enable actions on the repo?

Yes, because now they’re disabled by default - which is not something that we’d expect in repositories created from templates.
Previously, Actions were enabled - which made the template-based project fully operational.

I’ve raised this issue in the GitHub Education forum as well (see here for the thread). Like @dmusican my use case is education-focused and this change broke our workflow for providing automated feedback to students. It might seem trivial to ask students to push a button, but the workflow is designed around students not having to do that (and add to the cognitive load). I hope GitHub will consider reverting this change, especially considering we’re in the middle of one of the hardest semesters of our lives and are not in a position to help students in person.


Same experience with my classes. The Actions tab shows the state as disabled and has the button to enable. But at the same time going to the repository settings (as owner of the repository) and checking the Actions settings it does not say that the feature is disabled, it says “Actions permissions: Allow all actions”.

I also checked enabling this via API, but there is no such functionality.

Hello everyone, this issue has now been resolved. Actions are enabled on template repos now by default. It was a bug that was fixed that was fixed just now and has been pushed to production.


That’s great news! Thank you for sharing it, @hamelsmu!
I can confirm that Actions are enabled by default now in the project created from the template. :muscle:

Thanks. I have confirmed that our use-case works now - Repo creation using API with template “across” organizations. :+1: