will/github-changelog-generator
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Capitalization and full stops (#605)

Browse Source
This commit is contained in:
Ben Holden-Crowther 2017-12-15 15:01:04 +00:00 committed by Olle Jonsson
parent d9cf6ffd94
commit 8d0bb7d22d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -236,9 +236,9 @@ For example:
When you find a closed bug, it is very useful to know which release fixed it. When you find a closed bug, it is very useful to know which release fixed it.
So that you can easily find the issue by \# in `CHANGELOG.md`. So that you can easily find the issue by \# in `CHANGELOG.md`.
- it's not quite as easy to find this in handwritten releases notes - It's not quite as easy to find this in handwritten releases notes.
- a generated file saves you the trouble of remembering everything; - A generated file saves you the trouble of remembering everything;
sometimes people forget to add things to a handwritten file sometimes people forget to add things to a handwritten file.
Ultimately, I think GitHub Releases are ideal for end-users. Ultimately, I think GitHub Releases are ideal for end-users.
Meanwhile, `CHANGELOG.md` lives right in the repository, with its detailed list of changes, which is handy for developers. Meanwhile, `CHANGELOG.md` lives right in the repository, with its detailed list of changes, which is handy for developers.