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.
This enables a new trigger for keywords in the commit message or title. The usage is as follows:
Should only run if the keyword is matched.
or
Should not run if the keyword is matched.
I considered simplifying the notation by appending
*to each end of the keyword strings, but it would give the user less control on matching specific strings.Note: The way this is currently implemented follows the same syntax as other triggers, but requires adding the
Keywordcondition todrone-yaml. However, I see that the GitHub repository is currently archived, so I'm unable to open a PR.On further inspection it looks like drone-yaml
Conditionsessentially expects each argument to be a "path" in the matching operation. Passing an arbitrary string (message or title) will probably result in odd behavior. The solution here appears to be to simply create a separate Match function for Condition that uses gostrings.Containsand remove the wildcard operators above. Again, this is in drone-yaml, which appears to be private.