ytanikin/Conventional Commit In Pull Requests

Check that the PR title contains a valid task type and (optionally) a task number, and label the PR based on the task type

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
task_typesAn array of task types. Example: ["feat","fix","docs","test","ci","refactor","perf","chore","revert"]yes
ticket_key_regexRegular expression to match issue number in PR title, by default does not validate. Example ^PROJECT-\d{2,5}$no
add_labelWhether to add labelsnotrue
tokenGitHub token for applying labels.no${{ github.token }}
custom_labelsA JSON string mapping task types to custom label names. Example: {"feat": "feature", "fix": "fix", "docs": "documentation", "test": "test", "ci": "CI/CD", "refactor": "refactor", "perf": "performance", "chore": "chore", "revert": "revert", "wip": "WIP"}no

no outputs