Skip to content
Snippets Groups Projects
Select Git revision
  • bce6036a8e4d41c8ad3765726aa3973f7eeca4be
  • main default protected
  • renovate/main-zod-3.x
  • renovate/main-ghcr.io-renovatebot-base-image-10.x
  • renovate/main-ghcr.io-containerbase-devcontainer-13.x
  • next
  • revert-31645-feat/rename-gradle-wrapper-validation-action
  • renovate/main-redis-5.x
  • fix/36615b-branch-reuse-no-cache
  • chore/punycode
  • fix/36615-branch-reuse-bug
  • refactor/pin-new-value
  • feat/36219--git-x509-signing
  • feat/structured-logger
  • hotfix/39.264.1
  • feat/skip-dangling
  • gh-readonly-queue/next/pr-36034-7a061c4ca1024a19e2c295d773d9642625d1c2be
  • hotfix/39.238.3
  • refactor/gitlab-auto-approve
  • feat/template-strings
  • gh-readonly-queue/next/pr-35654-137d934242c784e0c45d4b957362214f0eade1d7
  • 41.28.2
  • 41.28.1
  • 41.28.0
  • 41.27.1
  • 41.27.0
  • 41.26.2
  • 41.26.1
  • 41.26.0
  • 41.25.1
  • 41.25.0
  • 41.24.0
  • 41.23.5
  • 41.23.4
  • 41.23.3
  • 41.23.2
  • 41.23.1
  • 41.23.0
  • 41.22.0
  • 41.21.4
  • 41.21.3
41 results

renovate

💡 commit-analyzer-cz

CI Go Report Card PkgGoDev

A Conventional Commits analyzer for go-semantic-release.

How the commit messages are analyzed

Bump major version (0.1.2 -> 1.0.0)

  • By adding BREAKING CHANGE or BREAKING CHANGES in the commit message footer, e.g.:
    feat: allow provided config object to extend other configs
    
    BREAKING CHANGE: `extends` key in config file is now used for extending other config files
  • By adding ! at the end of the commit type, e.g.:
    refactor!: drop support for Node 6

Bump minor version (0.1.2 -> 0.2.0)

  • By using type feat, e.g.:
    feat(lang): add polish language

Bump patch version (0.1.2 -> 0.1.3)

  • By using type fix, e.g.:
    fix: correct minor typos in code
    
    see the issue for details
    
    on typos fixed.
    
    Reviewed-by: Z
    Refs #133

Customizable Release Rules

It is possible to customize the release rules by providing options to the analyzer. The following options are available:

Option Default
major_release_rules *!
minor_release_rules feat
patch_release_rules fix

⚠️ Commits that contain BREAKING CHANGE(S) in their body will always result in a major release. This behavior cannot be customized yet.

Rule Syntax

A rule may match a specific commit type, scope or both. The following syntax is supported: <type>(<scope>)<modifier>

  • <type>: The commit type, e.g. feat, fix, refactor.
  • <scope>: The commit scope, e.g. lang, config. If left empty, the rule matches all scopes (*).
  • <modifier>: The modifier, e.g. ! for breaking changes. If left empty, the rule matches only commits without a modifier.
  • A * may be used as a wildcard for a type, scope or modifier.

Example Rules

Commit feat (or feat(*) *! (or *(*)!) chore(deps) *🚀
feat(ui): add button component
feat!: drop support for Go 1.17
chore(deps): update dependencies
refactor: remove unused code
fix🚀: correct minor typos

References

Licence

The MIT License (MIT)

Copyright © 2024 Christoph Witzko