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
For all the workflows we create, the below boilerplate almost always needs to be included, so that updating the workflow itself triggers the workflow (to test it before merging).
on:
pull_request:
paths:
- '.github/workflows/build.yml'
- 'dir/**'
For more complex workflows that rely on multiple composite workflows and calls other workflows, we end up with something verbose like below.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDProduct Feedback
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
The problem
For all the workflows we create, the below boilerplate almost always needs to be included, so that updating the workflow itself triggers the workflow (to test it before merging).
For more complex workflows that rely on multiple composite workflows and calls other workflows, we end up with something verbose like below.
Discovering and tracking these dependancies takes time and is error prone, especially if
sub-workflow-*.yml
call other composite actions themselves.Feature Request
Add an
on: workflow_modify
trigger a workflow if it's ownyml
is changed, or any of it's dependent workflowyml
files change.For example, to trigger the workflow when it's own
yml
is changedOr to trigger the workflow when itself or any dependent
yml
files are changedBeta Was this translation helpful? Give feedback.
All reactions