Product Help

CI/CD

Version Tagging

Version tagging for repositories is done via GitHub Actions. Tags will be automatically incremented based on the last created tag.

Standard Operating Procedure

Each commit must be in the following format and must be on the first line of the commit message:

Type: <major|minor|patch>[, Branch: <dev|test>]

Type must be included and is one of the following:

Type

Description

major

Major changes to the codebase

minor

Minor changes to the codebase

patch

Bug fixes or small changes to the codebase

Including Branch is optional, if excluded the tag will be created as production. It must be one of the following:

  • dev

  • test

Commit Message Examples

Below is an example commit message that will create the tag v#.#.#-dev and will increment the last # based on the last created tag.

Type: patch, Branch: dev This is my very detailed description of the commit.

Below is an example commit message that will create the tag v#.#.# and will increment the first # based on the last created tag.

Type: major This is my very detailed description of the commit.

Below is an example commit message that will create the tag v#.#.#-test and will increment the middle # based on the last created tag.

Type: minor, Branch: test This is my very detailed description of the commit.
Last modified: 28 January 2025