Don't trigger workflows for any release activities #152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #150. See the GitHub docs for additional context.
If you take a look at all of the workflow files of the jobs (linked in #150) which were triggered by release activities, you can see that only
feature
workflows were triggered since it was the only workflow that includedrelease: null
in itson
map.Accordingly, it seems like all we have to do to ensure workflows are not triggered on any release activity is omit the
release
item from theon
list in all of the workflow files.