How to skip a deployment job pointing at a particular environment if the current branch is not allowed to deploy to this environment? #131021
Replies: 1 comment
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi,
we are using https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-branches-and-tags to restrict which branches can be used to deploy to which environments.
Is there a way to skip (instead of failing with
Branch "foo" is not allowed to deploy to bar due to environment protection rules.
) a deployment job pointing at a particular environment if the current branch is not allowed to deploy to this environment?I know I can limit deployments to environment
bar
from branchfoo
and say:if: github.ref == 'refs/heads/foo'
in the job spec, but I would like to keep the relationship between branches and environments in a single place.Thanks!
Beta Was this translation helpful? Give feedback.
All reactions