diff options
author | Robert Speicher <rspeicher@gmail.com> | 2016-10-16 20:29:45 +0200 |
---|---|---|
committer | Robert Speicher <rspeicher@gmail.com> | 2016-10-16 21:05:24 +0200 |
commit | 9f7a7115a4c7b90e0203516f5aabf913ce02cbfe (patch) | |
tree | 6ae8abe8c0808a3449ac4569effa0532fd03c3ff /CONTRIBUTING.md | |
parent | f1fd2e4bab5485dc5b2073b7589378cd6c259cfb (diff) | |
download | gitlab-ce-9f7a7115a4c7b90e0203516f5aabf913ce02cbfe.tar.gz |
Convert CHANGELOG to Markdown
All this does is convert the version sections into headers. The list
items shouldn't really be indented by two spaces, but it makes no
difference to the rendering and this way we retain authorship history
for the actual changes.
Related to https://gitlab.com/gitlab-org/release-tools/merge_requests/29
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0cdcb54b0ae..b4635e50c28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -247,7 +247,7 @@ request is as follows: 1. Fork the project into your personal space on GitLab.com 1. Create a feature branch, branch away from `master` 1. Write [tests](https://gitlab.com/gitlab-org/gitlab-development-kit#running-the-tests) and code -1. Add your changes to the [CHANGELOG](CHANGELOG): +1. Add your changes to the [CHANGELOG.md](CHANGELOG.md): 1. If you are fixing a ~regression issue, you can add your entry to the next patch release (e.g. `8.12.5` if current version is `8.12.4`) 1. Otherwise, add your entry to the next minor release (e.g. `8.13.0` if |