Branch "x" is not allowed to deploy to github-pages due to environment protection rules.

[nad-au]

Select Topic Area

General

Body

I've created a new repository to host a private Pages site. We're on Enterprise. I'm using the recommended set-up for a Next Js site. Whether I deploy on main or any other branch I get this error.

I don't have any branch protection rules. I can push changes to any branch.

Please can you help me understand how to deploy a pages site? Or how to add or remove a protection rule so that I can deploy. Thanks.

[nad-au]

OK I've found the problem. Workflow creates an environment called github-pages which did indeed have a protection rule of branch master. Shortly after creating the repo I renamed default branch to main. So I had to update the env protection rule to match default branch and deployment worked.

[yoannchaudet]

Just wanted to add that this is a security mechanism. Any environment you deploy GitHub Pages to must be protected. By default we protect it with your repository's default branch.

[PetterGs]

Could this be elaborated on? Say I want to deploy from a branch called production. What do I need to do. I have no branch protection rules in my repo at all as far as I know.

[yoannchaudet]

We changed this behavior since my last message. As of today it is:

• If your site deploys with a branch source, the environment branch must be protected
• If your site deploys with a custom workflow (GitHub Actions source), the environment branch protection is optional (by default, we protect the github-pages environment with the repository's default branch, you can update this yourself or remove entirely the protection if you like)

[alberto56]

So I had to update the env protection rule to match default branch and deployment worked.

Just to elaborate on this, this can be done by visiting settings for your repo, then "Environments", then "github-pages", then changing the allowed branch.

[evgfilim1]

Hello. I have the same problem, action says it cannot deploy from branch, but it's a tag.

Protection rules:

[ragnarpa]

That started to happen out of the blue. GitHub, what is going on?

[jesshitchcock]

I am also experiencing this problem.

[jdogmcsteezy]

Me as well, but this behavior has been going on for some time for me.

[MathiasHaudgaard]

Having the same issue. 😞

[HenrySpartGlobal]

Had the same issue - I have heard you can contact GitHub support to revert the change for your account to the old version. But mid-September its going to be applied everywhere. GitHub engineering is working on getting something to fix these issues

https://github.com/orgs/community/discussions/62991#discussioncomment-6844269

[albertogodar]

I am having the same issue, what's the status of this please?

[ppptrevoro]

Same issue here, can't deploy from a tag with branch protection rule starting yesterday

[fesaab]

Same issue here... It started to happen yesterday.

[dmikurube]

Same here for a tag. :(

However, this topic may be unrelated. I posted another discussion for the tag issue:
https://github.com/orgs/community/discussions/63890

[ap-vishal]

We are also having the same issue, it started happening on 10th August and it is probably due to this: https://github.blog/changelog/2023-08-10-actions-runs-triggered-from-tags-or-forks-with-the-same-name-as-a-protected-branch-will-now-be-blocked/

Right now, it breaks all of our projects.

[Tautorn]

Same issue here, I can't trigger build because github actions are returning is not allowed to deploy to prod due to environment protection rules.. There's no protection rule for that case. All projects are broken.

[ivoivaka]

This is currently happening within our project also. For example, previous version was deployed successfully through the workflow and it was "v0.10.2", now it's failing due to protection rules

[calebyouki]

it seems like GitHub doesn't know the difference between branches and tags

[mhw0]

Same issue:

[cbarbian-sap]

Same here. We are deploying to github-pages from releases which have semver tags. In the past, we allowed a pattern [0-9].* (which is clearly not optimal), but even that is not working anymore now.

The only solution that works for us now is to allow all branches, which is obviously much worse. Is that really the plan?

[sunrawat]

instead of / use ./

[ashe-li]

withastro/docs#1376

works for me

[rikhuijzer]

Another cause for this problem can be that the GitHub Pages source is set to "Deploy from branch" at

https://github.com/<REPOSITORY_OWNER>/<REPOSITORY_NAME>/settings/pages

To fix it, set the source to "GitHub Actions". This fixed it for me on a repository which used to use gh-pages branch and switched to actions/deploy-pages@v4.