Branch X is not allowed to deploy to X due to environment protection rules.

[ejohnsonzagg]

Select Topic Area

Question

Body

We are using the free tier of GitHub with a private repository, but we are seeing an error during deployments to our dev environment of "Branch X is not allowed to deploy to X due to environment protection rules.". Since we are on the free tier, we don't have environment protection rules and I've also made sure any branch specific rules have been disabled. We are able to deploy our "staging" branch successfully, but a branch by any other name fails. Just 4 days ago we were able to deploy any branch with any name successfully and there have been no code changes or GitHub config changes on our side in that time.

[ThiagoSousa81]

Hi, I've identified a list of possible factors that could be causing this issue:

1. Check Branch Protection Rules:

• Even on the free tier, you can configure branch protection rules. Check if there are any active branch protection rules that could be preventing the deployment. For more details, see the protected branches documentation.

2. Check Environment Protection Settings:

• Make sure there are no environment protection settings that could be causing the issue. Although you mentioned that you are on the free tier, it's a good idea to review the settings to make sure there isn't something that you've inadvertently configured.

3. Disable Branch-Specific Rules:

• Make sure that all branch-specific rules are disabled. There may be a setting that is causing the issue. For more information on managing branch protection rules, see managing branch protection rules.

4. Confirm Deployment Permissions:

• Make sure that deployment permissions have not been accidentally changed. Check your collaborator permissions and deployment settings to make sure everything is set up correctly.

5. Check for Branch Name Patterns:

• There may be branch name patterns that are being automatically protected. For example, if there is a rule to protect all branches that contain certain keywords, that may be causing the issue. Check the protected branches documentation for branch naming patterns.

If these checks do not resolve the issue, I recommend contacting GitHub support for further assistance.

Good project 👍

References:

• About protected branches
• About branches

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬