Git commit messages

BALSAMIC is loosely following a system to standardize the commit messages. And following up from commit messages discussed on https://github.com/Clinical-Genomics/development/pull/97 , the format below is strongly recommended for commit messages:

Subject line

Subject can include one of the following:

1. feat: Introducing a new features. This includes but not limited to workflows, SnakeMake rule, cli, and plugins. In other words, anything that is new and fundamental change will also go here. Enhancements and optimizations will go into refactor.
2. fix: This is essentially a patch. Included but not limited to: bug fixes, hotfixes, and any patch to address a known issue.
3. doc: Any changes to the documentations are part of doc subject line, included but no limited to: docstrings, cli-help, readme, tutorial, documentation, CHANGELOG, and addition of ipython/jupyter notebook in form of tutorial.
4. test: Any changes to the tests are part of test subject line. This includes adding, removing or updating of the following: unittests, validation/verification dataset, and test related configs.
5. refactor: Refactoring refers to a rather broad term. Any style changes, code enhancement, and analysis optimization.
6. version: Any changes to .bumpversion config and or change of version will be specified with this. This includes comments within .bumpversion, structure of .bumpversion, etc.

Scope

Scope is specified within parenthesis. It show the scope of the subject line. The following scope are valid:

• cli
• style
• rule (refers to SnakeMake rules)
• workflow (refer to SnakeMake workflows)
• config (refers to configs that are either used or generated by BALSAMIC)
• Relevant scopes that might fit into a scope description

Note: If scope is broad or matching with multiple (it shouldn't, but if it does) one can leave out the scope.

Message

It's better to start Git commit message with the following words:

• added
• removed
• updated