Repository navigation
feat: comment on unmatched branches instead of failing by default - #254
Merged
Merged
Conversation
Unmatched branches no longer fail the workflow by default. The action logs a warning and continues; a pull request comment can be enabled independently. - Add commentOnUnmatchedPattern (default false), comment, and github-token inputs - Default failOnUnmatchedPattern to false - Keep comment posting and failing independently configurable - Resolve the pull request from the event payload or GITHUB_REF - Upsert a single comment via a hidden marker - Warn instead of failing when the comment cannot be posted
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.
Unmatched branches no longer fail the workflow by default. The action logs a warning and continues; a pull request comment can be enabled independently.