Browse Source

Fix formatting

restructure
Garrit Franke 3 years ago
parent
commit
854d29dfe2
  1. 3
      content/posts/2021-02-20-changelogs.md

3
content/posts/2021-02-20-changelogs.md

@ -33,7 +33,6 @@ This is just an example that illustrates how **I** decided to note down my chang
Here's an example of how a changelog could look like. It's taken from [Sabre](https://github.com/garritfra/sabre), a project I'm currently working on. The full changelog can be found [here](https://github.com/garritfra/sabre/blob/master/CHANGELOG.md).
```md
# Changelog
## v0.4.0 (2021-02-20)
@ -89,11 +88,11 @@ I'd also advise you to keep a log of your commits in the description of the tag.
```
git tag -a <new release> -m "$(git shortlog <last release>..HEAD)"
```
So, if you're releasing version `v0.2.0` after `v0.1.5`, you would run this command to tag your current commit with a good commit history:
```
git tag -a v0.2.0 -m "$(git shortlog v0.1.5..HEAD)"
```
This is post 013 of [#100DaysToOffload](https://100daystooffload.com/).

Loading…
Cancel
Save