Prevent github actions from automatically creating an environment that doesn't exist

[a-jackson]

Select Topic Area

Question

Body

If a workflow references an environment that doesn't exist. Github Actions just creates it. We've got environments set up with protection rules such as required approvals, but we just had a case with a misspelled environment name and the action made a new environment with no approval required and then ran the deployment.

Is there any way to stop this behaviour?

[salvianreynaldi]

Hopefully this crucial capability will be available soon,
the workaround is to add manual checks via GitHub rest API

[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! 💬

[anthonwellsjo]

👍🏻 I really don't love current behaviour.

[sawantyogita]

Select Topic Area

Question

Body

If a workflow references an environment that doesn't exist. Github Actions just creates it. We've got environments set up with protection rules such as required approvals, but we just had a case with a misspelled environment name and the action made a new environment with no approval required and then ran the deployment.

Is there any way to stop this behaviour?