Skip to content

Commit 87400b9

Browse files
committed
chore: update README
1 parent 3bfb5f4 commit 87400b9

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
# Conventional Commits Versioner
22

3-
![Tag and Release](https://github.com/smlx/ccv/workflows/Tag%20and%20Release/badge.svg)
4-
[![Coverage Status](https://coveralls.io/repos/github/smlx/ccv/badge.svg?branch=main)](https://coveralls.io/github/smlx/ccv?branch=main)
3+
[![Release](https://github.com/smlx/ccv/actions/workflows/release.yaml/badge.svg)](https://github.com/smlx/ccv/actions/workflows/release.yaml)
4+
[![coverage](https://raw.githubusercontent.com/smlx/ccv/badges/.badges/main/coverage.svg)](https://github.com/smlx/ccv/actions/workflows/coverage.yaml)
55
[![Go Report Card](https://goreportcard.com/badge/github.com/smlx/ccv)](https://goreportcard.com/report/github.com/smlx/ccv)
6-
[![Go Reference](https://pkg.go.dev/badge/github.com/smlx/ccv.svg)](https://pkg.go.dev/github.com/smlx/ccv)
76

87
`ccv` does one thing: it walks git commit history back from the current `HEAD` to find the most recent tag, taking note of commit messages along the way.
98
When it reaches the most recent tag, it uses the commit messages it saw to figure out how the tag should be incremented, and prints the incremented tag.

0 commit comments

Comments
 (0)