| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
A "Changelog" is a record of all notable changes made to a project. Such a changelog, in our case the :file:`CHANGELOG.rst`, is read by our users. Therefor, any description should be aimed to users instead of describing internal changes which are only relevant to developers.
To avoid merge conflicts, we use the Towncrier package to manage our changelog.
The directory :file:`changelog.d` contains "newsfragments" which are short ReST-formatted files. On release, those news fragments are compiled into our :file:`CHANGELOG.rst`.
You don't need to install towncrier yourself, use the :command:`tox` command to call the tool.
We recommend to follow the steps to make a smooth integration of your changes:
After you have created a new pull request (PR), add a new file into the directory :file:`changelog.d`. Each filename follows the syntax:
<ISSUE>.<TYPE>.rst
where <ISSUE> is the GitHub issue number. In case you have no issue but a pull request, prefix your number with pr. <TYPE> is one of:
For example: 123.feature.rst, pr233.removal.rst, 456.bugfix.rst etc.
Create the new file with the command:
tox -e changelog -- create 123.feature.rst
The file is created int the :file:`changelog.d/` directory.
Open the file and describe your changes in RST format.
Check your changes with:
tox -e changelog -- check
Optionally, build a draft version of the changelog file with the command:
tox -e changelog
Commit all your changes and push it.
This finishes your steps.
On release, the maintainer compiles a new :file:`CHANGELOG.rst` file by running:
tox -e changelog -- build
This will remove all newsfragments inside the :file:`changelog.d` directory, making it ready for the next release.
| Back | FazBrowse Home | New Git URL |