Branch Name Lint

Usage

Globally

1> npm install @b12k/branch-name-lint -g
2> branch-name-lint

As development dependency

1> npm install @b12k/branch-name-lint -D
2> npm set-script lint:branch-name "branch-name-lint"

With custom branch names

1> branch-name-lint --name=my-custom/branch-name

Git hook

Using simple-git-hooks

package.json

1{
2  "simple-git-hooks": {
3    "pre-push": "branch-name-lint"
4  }
5}

Alternatevly you can use it with husky.

Configuration

Config schema

1interface Config {
2  pattern: string;
3  params: Record<string, string[]>;
4  prohibited: string[];
5}

User provided configuration

Under the hood BranchNameLint uses cosmicconfig to load its configuration.

You can create one of the following:

• branchnamelint property in the package.json file
• Extensionless "rc file" in .json or .yaml format
  • .branchnamelintrc
• "rc file" with .json or .yaml extensions
  • .branchnamelintrc.json
  • .branchnamelintrc.yaml
• "rc file" with .js extension
  • .branchnamelintrc.js
• ".config.js" file
  • branchnamelint.config.js

don't forget to do module.exports = {...} in .js config files

BranchNameLint will merge found configuration with its defaults.

Default configuration

1module.exports = {
2  pattern: ':type/:name',
3  params: {
4    type: [
5      'fix',
6      'docs',
7      'misc',
8      'improve',
9      'introduce',
10    ],
11    name: ['[a-z0-9-]+'],
12  },
13  prohibited: [
14    'ci',
15    'wip',
16    'main',
17    'test',
18    'build',
19    'master',
20    'release',
21  ],
22};

Linting

BranchNameLint uses path-to-regexp to check if branch name matches the pattern provided in config.

Firstly branch name will be checked if its prohibited or not. On the next step, if params are provided, pattern parts will be modified/populated using respective keys. For example:

1(default configuration)
2:type/:name => :type(feature|fix|misc|docs)/:name([a-z0-9-]+)

Please refer to path-to-regexp docs for advanced patterns.

Configuration recipes

Only check for protected branches

1module.exports = {
2  pattern: '', // or other falsy value: undefined | 0 | null | false
3  params: {},
4  prohibited: [
5    'master',
6    'main',
7    'build',
8    'test',
9    'wip',
10    'ci',
11    'release',
12  ],
13};

Dot-separated username & issue id

b12k.fix/example-branch-description/lbn-12345

1module.exports = {
2  pattern: ':username.:type/:desc/:issue',
3  params: {
4    type: [
5      'feature',
6      'fix',
7      'misc',
8      'docs',
9    ],
10    issue: ['lbn-[a-z0-9-]+'],
11  },
12  prohibited: [
13    'master',
14    'main',
15    'build',
16    'test',
17    'wip',
18    'ci',
19    'release',
20  ],
21};

Scopes for monorepo

feature/my-awesome-app/yet-another-great-feature

1(imaginary monorepo structure)
2root/
3    apps/
4        my-awesome-app
5        another-great-app
6    libs/
7        very-useful-lib
8        shared-lib
9    .branchnamelintrc.js

1const fs = require('fs');
2
3const readDirectories = (path) => fs
4  .readdirSync(path, { withFileTypes: true })
5  .filter((file) => file.isDirectory())
6  .map(({ name }) => name);
7
8module.exports = {
9  pattern: ':type/:scope/:description',
10  params: {
11    type: [
12      'feature',
13      'fix',
14      'misc',
15      'docs',
16    ],
17    scope: readDirectories('./apps')
18  },
19  prohibited: [
20    'master',
21    'main',
22    'build',
23    'test',
24    'wip',
25    'ci',
26    'release',
27  ],
28};