You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the latest environment.js code in the repo.
In settings.yml when wanting to create an environment when the same name environment is already there. We get a 404 during PR mode which crashes the app. Possibly also happens on main.
What is actually happening
What happens is that the existing environment has protected_branches: true which is mutually exclusive with deployment-branch-policies.
In PR mode a 404 then happens because it wrongly requests to list the custom branch policies. This results in a crash of the app.
The environment we want to update has custom deployment branch policies setup:
Problem Description
Using the latest environment.js code in the repo.
In settings.yml when wanting to create an environment when the same name environment is already there. We get a 404 during PR mode which crashes the app. Possibly also happens on main.
What is actually happening
What happens is that the existing environment has
protected_branches: true
which is mutually exclusive with deployment-branch-policies.In PR mode a 404 then happens because it wrongly requests to list the custom branch policies. This results in a crash of the app.
The environment we want to update has custom deployment branch policies setup:
What is the expected behavior
When you get the environment you see if it has protected_branches set to true. If false, only then do you try to retrieve custom_branch_policies.
Error output, if available
Context
Are you using the hosted instance of probot/settings or running your own?
If running your own instance, are you using it with github.com or GitHub Enterprise?
Version of probot/settings
Version of GitHub Enterprise
The text was updated successfully, but these errors were encountered: