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
In our project, we are setting up a new actions workflow, which triggers on a PR merge (using a combination of PR close and filter github.event.pull_request.merged == true). We also have set up environment specific branch protections rules for example, we have three branches called development, test and production and only development branch can deploy using the development environment. It is here that we run into problems, when we merge a pull request from development to test, I expect the triggering to come from the test branch based on the below trigger condition
pull_request: types: - closed branches: - 'test'but in my case the workflow for test is triggered but the triggering branch is development, the branch from which the pull request originated, due to this , the deployment to test environment fails since branch protection mentioned above does not allow development branch to deploy into test.
Can somebody help me with this issue?
Beta Was this translation helpful? Give feedback.
All reactions