Ruleset: Workflow defined as required in ruleset does not triggered correctly #106795
Replies: 1 comment
-
This behaviour is documented in the rulesets documentation: https://docs.github.com/en/enterprise-cloud@latest/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#supported-event-triggers
In my case, I have a workflow that checks if auto-merge is enabled and if the auto-merge commit message follows the conventional commits specification. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi all,
I've got a problem with a workflow I would like to enforce as per organizational ruleset with "Require workflows to pass before merging". The ruleset is enforced on repository A.
The workflow referenced in the ruleset resides in repository B and is triggered with the following:
pull_request:
types:
- opened
- edited
- reopened
Upon opening a pull request in repository A, the workflow triggers as expected.
However, when editing the title of the pull request in repository A, the workflow is not triggered again.
When closing & reopening the pull request, the workflow is triggered again.
I assume rulesets don't evaluate when a pull request is edited, so the triggers of the workflow that is to be enforced are not taken into consideration?
Thanks for your support!
Beta Was this translation helpful? Give feedback.
All reactions