Reverse the order of CHANGELOG entries (#681)

It's more consistent to prepend entries to the [Unreleased] section of
the changelog, so that entries are all in reverse-chronological order.
Since we've appended the first few entries, we reverse them now.

Test plan: Not needed
This commit is contained in:
Dandelion Mané 2018-08-16 11:14:52 -07:00 committed by GitHub
parent e68fe19487
commit f1afd5a248
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 5 deletions

View File

@ -1,9 +1,11 @@
# Changelog # Changelog
## [Unreleased] ## [Unreleased]
- Start tracking changes in `CHANGELOG.md`
- Aggregate over connection types in the cred explorer (#502)
- Support hosting SourceCred instances at arbitrary gateways, not just the root of a domain (#643)
- Display version string in the app's footer
- Rename cred explorer table columns (#680) - Rename cred explorer table columns (#680)
- Display version string in the app's footer
- Support hosting SourceCred instances at arbitrary gateways, not just
the root of a domain (#643)
- Aggregate over connection types in the cred explorer (#502)
- Start tracking changes in `CHANGELOG.md`
<!-- Please add new entries to the _top_ of this section. -->

View File

@ -123,7 +123,8 @@ This is the same set of tests that is run on our CI system, Travis.
If your patch makes a change that would be visible or interesting to a If your patch makes a change that would be visible or interesting to a
user of SourceCred—for example, fixing a bug—please add a description of user of SourceCred—for example, fixing a bug—please add a description of
the change under the `[Unreleased]` heading of `CHANGELOG.md`. the change under the `[Unreleased]` heading of `CHANGELOG.md`. Your new
change should be the first entry in the section.
## When writing commit messages ## When writing commit messages