feat(match): matches by PR title and body #688
+353
−33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
documentation
kalvarez2
force-pushed
the
feat/filter-by-pr-body-or-title
branch
from
a062d48
to
1884eaf
Compare
Closed
|
@kalvarez2 any chance we can pick this back up? Would love this feature to be available in this action. @MaksimZhukov is this something this action is interested in? |
|
Would like to follow up on this as an alternative to using https://github.com/Bhacaz/label-regex |
|
This would be useful for us as well, using branch names can catch some of the PRs I'd like to label, but I suspect we'll miss a bunch which might have a keyword we could use in the PR description or title. My use case is to label incident-related PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Enhances the glob matchers to support matching a text on PR title or body.
The change is backwards compatible, no need to change the existing configurations. Any and All continue to work.
The matchers now support prefix "title:" and "body:"
Simple example:
label1:
=>Would add the label "label1" if the body contains the string #potato
The existing all and any continue to work:
isText:
=> Would set the label isText if both all the files have extension txt, and the body contains "#isOnlyText"
The change is backwards compatible, but documentation changes with examples are also included, comments / enhancements are very welcome.
Related issue:
#55
Check list: