Developer Instructions

Contents:

Automatic Versioning

You must follow the conventional commit messages pattern when contributing to this repository!

Conventional Commits: A specification for adding human and machine readable meaning to commit messages.

The commit message should be structured as follows:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Consider reading the summary if you don't know anything about the available types.

The pipeline uses the npm package semantic-release internally. Take a look at the release-workflow or the official documentation if you want to know more about it.

Also, note that it uses the default GITHUB_TOKEN for interacting with GitHub. .

Docker image tagging happens in the build action according to SemVer. It uses the docker/metadata-action: