fix: remove optional create PR pattern input for consistency in commit message validation#3
Merged
srajasimman merged 1 commit intomainfrom Sep 22, 2025
Merged
Conversation
…t message validation
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
1 participant
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 simplifies the configuration of commit message validation by removing the ability to customize the regex pattern through the GitHub Action's inputs. The validation logic now relies on a fixed set of patterns within the code.
Configuration simplification:
patterninput fromaction.yml, so users can no longer specify a custom regex for commit message validation.Validation logic update:
commit-message-validator.jsto use a hardcodedcreatePrPatterninstead of reading it from action inputs, ensuring consistent validation behavior.