Repository navigation
feat: comment on unmatched branches by default - #259
Merged
Merged
Conversation
Change commentOnUnmatchedPattern to default to true so an unmatched branch posts or updates a pull request comment without extra configuration. Setting the input to false disables commenting. Update the README behavior table, examples, and tests to reflect the new default.
This file contains hidden or 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
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.
This pull request changes the default behavior for posting comments on pull requests when a branch does not match any specified patterns. Now, a comment is posted by default unless explicitly disabled. The documentation, input handling, and tests have all been updated to reflect this new default.
Default behavior change:
commentOnUnmatchedPatterninput now defaults totrue, so a comment will be posted on the pull request when the branch does not match any pattern, unless set tofalse. [1] [2] [3] [4]Documentation updates:
README.mdto describe the new default behavior for unmatched branches, including revised examples and option tables. [1] [2] [3] [4] [5]Test updates:
runner_test.goto verify that commenting is enabled by default and can be disabled by settingcommentOnUnmatchedPattern: false. [1] [2] [3]