dwtechs / gitbranchvalidator Goto Github PK

• Synopsis
• Motivation
• Installation
  • npm
  • Yarn
  • Local
• Usage
  • Command line
  • Patterns
  • Message
  • Prompt
  • Help
  • Workflow integration
• Contributors
• License
• Stack
• Dependencies

GitBranchValidator is an open source git branch name validator library.

The goal of this library is to provide an easy way to check if the current branch name is valid before pushing it to the remote.

It's a good way to help developers keep their branch names clean on the repository and facilitate the workflow of a project with strict naming rules.

The default pattern follows the principles described here.

You can also set your own rules using custom patterns.

You can validate commit messages as well with GitCommitValidator

This library is written in Node.js. You must install Node.js and npm in order to run it.

$ npm i @dwtechs/gitbranchvalidator -g

$ yarn add @dwtechs/gitbranchvalidator -g

Alternatively, if you are planning to use GitBranchValidator within your npm package only or with npx you can install it as a devDependency in your project.

$ npm i @dwtechs/gitbranchvalidator --save-dev

$ yarn add @dwtechs/gitbranchvalidator --dev

This library is meant to be used in "pre-commit", "commit-msg" or/and "pre-push" Git hook. Thus it is not bound to Javasrcipt applications only and can be used by any git repository.

You can learn more about Git hooks and how ti cutomize them in the Git Manual

Because hooks aren’t transferred with a clone of a project, you must distribute these scripts some other way and then have your users copy them to their .git/hooks directory and make them executable. You can distribute these hooks within the project or in a separate project, but Git will not set them up automatically for you.

$ gbvalidator

Alternatively if you did not install GitBranchValidator globally you can use npx.

$ npx gbvalidator

Or as an npm script in your package.json.

{
  "scripts": {
    "commit": "gbvalidator"
  }
}

• Default : ^(feat|fix|test|doc)/[A-Z0-9-#]{2,25}/[a-z0-9_-.]{3,40}$
• Release : ^release/v[a-z0-9+-.]{3,25}$

The patterns follow the principles described here.

You can use your own custom patterns by adding an optional regexp :

$ cd <git-project>
$ gbvalidator --patterns "^(feat|fix)\\/([a-z0-9_#-\\.\\/]){3,50}$"

You can use several patterns if needed :

$ gbvalidator --patterns "pattern1" "pattern2" "pattern3"

If one of them is valid, the branch name will be valid.

You can customize the end of the error message :

$ gbvalidator --message "You can learn more about branch name conventions of this project on https://dwtechs.github.io/efficient-git/branch/"

If the branch name is not valid, the process will be blocked by default. You can use the option "--continue" to prompt the user instead.

$ gbvalidator --continue

In this case the user will be prompted about the invalid branch. He will be able to keep going if he choose so.

Git hooks are not run in an interactive environment. So this option will fail if used in a Git hook.

You can access the documentation by passing the "help" parameter :

$ gbvalidator --help

Validate branch name on pre-push hook by adding the following code in the .git/hooks/pre-push file :

gbvalidator

Or with tools like Husky In the package.json file :

{
  "husky": {
    "hooks": {
      "pre-push": "gbvalidator"
    }
  }
}

You can do it with any other tool, or work on Git hooks directly.

You can use GitCommitValidator in the "commit-msg" hook as well :

gbvalidator && gcvalidator -src "$1"

You can find git hooks examples in the ./hooks/ folder. To install them just paste them in the .git/hooks/ folder of your repositories.

GitBranchValidator is still in development and I would be glad to get all the help you can provide for this project. To contribute please read contributor.md for detailed installation guide.

MIT