luzifer/git-changerelease
1
0
Fork 0
mirror of https://github.com/Luzifer/git-changerelease.git synced 2024-10-18 06:04:20 +00:00
Code Issues Releases Wiki Activity
git-subcommand to write the changelog in a consistent format and tag it using semantic versioning
51 commits 1 branch 19 tags 1.1 MiB
Shell 60.1%
Go 34.5%
Makefile 5.4%
Find a file
Knut Ahlers 0bd66ae67a
Replace broken project status 
Signed-off-by: Knut Ahlers <knut@ahlers.me>
2020-08-07 16:27:07 +02:00
assets Add logic to ignore commit messages 2018-09-26 10:55:29 +02:00
integration Add integration tests 2017-05-31 14:51:23 +02:00
.gitignore add the initial version 2016-07-14 12:55:04 +02:00
.repo-runner.yaml Update reporunner image 2018-07-02 16:47:40 +02:00
assets.go Replace error concat with wrapping 2020-08-07 16:05:08 +02:00
config.go Add logic to ignore commit messages 2018-09-26 10:55:29 +02:00
git.go fix wrong bump when patch and minor are included 2016-07-21 17:51:08 +02:00
go.mod Replace error concat with wrapping 2020-08-07 16:05:08 +02:00
go.sum Replace error concat with wrapping 2020-08-07 16:05:08 +02:00
History.md prepare release v0.9.0 2018-09-26 10:55:45 +02:00
LICENSE Fix License file 2018-07-02 16:55:13 +02:00
main.go Lint: Cleanup code a little 2020-08-07 16:19:02 +02:00
Makefile Move to go modules 2020-08-07 15:47:29 +02:00
README.md Replace broken project status 2020-08-07 16:27:07 +02:00
semver.go refactor code, follow linter advices 2018-07-03 09:46:37 +02:00
semver_test.go refactor code, follow linter advices 2018-07-03 09:46:37 +02:00

README.md

Go Report Card

Luzifer / git-changerelease

git-changerelease is a git-subcommand to write the changelog in a consistent format and tag it using semantic versioning. You can see the version it writes in the History.md file in this repository.

Features

  • Specify regular expressions to match the commit subject against for automated detection of major / minor / patch releases
  • Automatically write Changelog from commits
  • Start editor to change the Changelog (and the version) before tagging

Usage

  • Generate a configuration file using git changerelease --create-config
  • Edit your matchers in the configuration file just created
  • Commit and release:
# git init
Initialized empty Git repository in /tmp/test/.git/

# git commit --allow-empty -m 'add an empty commit'
[master (root-commit) 0cc02e6] add an empty commit

# git-changerelease
# git describe --tags HEAD
v0.1.0

# git commit --allow-empty -m 'fix another empty commit'
[master 69d6f0e] fix another empty commit

# git-changerelease
# git describe --tags HEAD
v0.1.1