abhinavsingh06/Pull Request title rules
Github action to enforce Pull Request title conventions
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Sep 14, 2021
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: abhinavsingh06/pr-title@fafca8a80ee14ffedd114d9b7c45cd748322621e # no releases — HEAD as of 2026-07-16tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| regex | Regex to validate the pull request title | no | .+ |
| allowed_prefixes | Comma separated list of prefix allowed to be used in title. eg: feature,hotfix,JIRA- | no | "" |
| disallowed_prefixes | Comma separated list of prefix disallowed to be used in title. eg: feat,fix | no | "" |
| prefix_case_sensitive | Are the allowed & disallowed prefixes case sensitive? | no | false |
| min_length | Min length of title | no | 1 |
| max_length | Max length of title. -1 to ignore the rule | no | -1 |
| github_token | Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the PAT. We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. | no | ${{ github.token }} |
Outputs
no outputs