MfGames Conventional Commit


A small utility that calculates the sematic version from conventional commits in a Git repository.

This utility does one thing only, calculate the [semantic version] from Git commits that conform to the [conventional commit] specification. It is path-aware which means only commits inside certain directories are included in the calculation. The current version number is built from the highest sematic version tag found in the commit's parents.

For example, the version of “Package1” will be 1.2.4 and “Package2” will be 1.3.0 from the following commits:

$ git log --name-only # filter out unimportant bits
    fix: fixing package1


    feat: fixing package2


    fix: sweeping change


    feat: current version # tagged "Package1-1.2.3" and "Package2-1.2.3"


In the above example, the second commit is ignored while calculating the “Package1” commits which will have a new version of “1.3.0” because of the “feat” commit. While calculating “Package2”, the version will be “1.2.4” because of the “fix” in the second commit because the first is ignored.

If a version cannot be found, this will use 0.0.1.


Configuration is done via a file checked into the Git root in .config/mfgames-conventional-commit.json. An example file is below:

  "$schema": "",
  "packages": {
    "Package1": {
      "tag_prefix": "Package1-*",
      "paths": { "include": ["src/package1/**/*"] }
    "Package2": {
      "tag_prefix": "Package2-*",
      "paths": { "include": ["src/package2/**/*"] }

To use this in a single package repository, the following can be used:

  "$schema": "",
  "packages": {
    "default": {
      "tag_prefix": "v*",
      "paths": { "include": ["**/*"] }

At the moment, configuration has poor error handling, so if the program says it cannot read the configuration file, check the file. The schema will change “soon”.


The executable is mfgames-conventional-commit.

mfgames-conventional-commit --package Package1


--directory PATH

The directory (or sub-directory) inside the Git repository. If this is not provided, then the current working directory will be used.

--package NAME


The name of the package, case-sensitive, that matches the package name inside the configuration. This can be used anywhere within the Git repository, not just within the directories for that project.

In the future, this will not be required if run inside a directory that only exists inside a single project.

-v, --verbose

Increase the level of verbosity. At default, this will only show warnings and errors on stderr and write out the calculated version on stdout. When this option is given (three levels), it will write out increasingly more information about how the version is calculated.