GitVersion.yml

mode: ContinuousDeployment
branches:
  main:
    tag: beta
    increment: Patch
  release:
    tag: rc
  pull-request:
    tag: pr

#Custom commit messages to support Conventional Commit and DevMoji syntax

#Reference: https://regex101.com/r/xdUFkI/1
major-version-bump-message: 💥|:boom:|BREAKING CHANGE:|\+semver:\s?(breaking|major)
#Reference: https://regex101.com/r/hegWXh/1
minor-version-bump-message: ✨|:(feat|tada):|^feat:|\+semver:\s?(feature|minor)
#Reference: https://regex101.com/r/NACNiA/1
patch-version-bump-message: '[📌🐛🩹🚑♻️🗑️🔥⚡🔒➕➖🔗⚙️]|:(bug|refactor|perf|security|add|remove|deps|config):|^(fix|refactor|perf|security|style|deps):|\+semver:\s?(fix|patch)'
#Reference: https://regex101.com/r/Kw8oen/1
no-bump-message: '[📝📚🎨🚨💡🧪✔️✅☑️🚀📦👷🌐🔧]|:(docs|style|test|test_tube|release|build|ci|i18n|chore|heavy_check_mark|white_check_mark|ballot_box_with_check):|^(docs|style|test|release|build|ci|i18n|chore):|\+semver:\s?(none|skip)'

#Set the build numbers to be xxx, example 0.1.0-myfeature001 or 0.2.1-beta001. This allows for longer feature branch names, and can be increased for more active projects
#You should set this to the number of commits you expect to have for a given branch before merging.
#For instance, if vNext is never going to contain more than 99 commits before you push it to master as a new version, you can set this to 2. 3 is good for all but the largest projects.
#BUG: Cannot use anything other than 4 until this is fixed: https://github.com/GitTools/GitVersion/issues/2632
legacy-semver-padding: 4
build-metadata-padding: 4
commits-since-version-source-padding: 4