A CLI tool to validate Git branch names using Conventional Branch guidelines. This package ensures that your branch names follow consistent naming conventions—supporting core branches like main, master, and develop, as well as structured feature, bugfix, hotfix, and release branches.
Install the package globally using npm:
npm install -g validate-branchOr add it as a development dependency in your project:
npm install --save-dev validate-git-branchOnce installed, run the CLI command in your Git repository:
validate-branchThe tool will fetch the current Git branch name and validate it against the conventional naming rules. If the branch name is valid, you'll see a success message; otherwise, an error message will guide you to use the correct format.
You can integrate this tool with Git hooks to enforce branch naming on every commit or push. For example, using Husky:
npx husky add .husky/pre-push "validate-branch"Your branches should follow one of the following patterns:
-
Core Branches:
mainmasterdevelop
-
Feature, Bugfix, and Hotfix Branches:
feature/branch-namebugfix/branch-namehotfix/branch-name
-
Release Branches:
release/branch-name- Release branches may include dots (e.g., release/v1.2.0)
The tool uses a refined regular expression to ensure that only the proper characters and structure are allowed for each branch type.
If you encounter a bug or want to see something added/changed, please go ahead and open an issue ! If you need help with something, feel free to start a discussion!
This project is licensed under the MIT License.
For support or any questions, please open an issue in the GitHub repository or contact backendwithali@gmail.com.