branch-name-validation

Commit policy as code for teams and AI agents: commit messages, branch names, authors, sign-offs, tags, files and AI attribution, checked from one config file.

Commit policy as code on every pull request: the GitHub Action for Commit Check.

Flexible git branch name linter with some extra validating features

Checks if newly created branches follow a convention defined within a regular expression

GitHub Action that checks if the current branch name matches a specified regex pattern. This is particularly useful for enforcing branch naming conventions in your repositories.

NodeJS starter template with Conventional commit & lint, branch name validation, ESLint, Prettier, Husky and Release with auto generation of Conventional CHANGELOG.md file with versioning

A CLI and GitHub Action that validates issue references actually exist in your GitHub repository - not just pattern matching, but real verification of commit messages (#123), branch names (feature/123, 123-fix-bug), PR titles, or any text.