|
|
|
@ -48,6 +48,26 @@ Please ensure your changes match the cosmetic style of the existing project, |
|
|
|
|
and **never** mix cosmetic and functional changes in the same commit, as it |
|
|
|
|
makes it horribly hard to review otherwise. |
|
|
|
|
|
|
|
|
|
Changelog |
|
|
|
|
~~~~~~~~~ |
|
|
|
|
|
|
|
|
|
All changes, even minor ones, need a corresponding changelog |
|
|
|
|
entry. These are managed by Towncrier |
|
|
|
|
(https://github.com/hawkowl/towncrier). |
|
|
|
|
|
|
|
|
|
To create a changelog entry, make a new file in the ``changelog.d`` |
|
|
|
|
file named in the format of ``issuenumberOrPR.type``. The type can be |
|
|
|
|
one of ``feature``, ``bugfix``, ``removal`` (also used for |
|
|
|
|
deprecations), or ``misc`` (for internal-only changes). The content of |
|
|
|
|
the file is your changelog entry, which can contain RestructuredText |
|
|
|
|
formatting. A note of contributors is welcomed in changelogs for |
|
|
|
|
non-misc changes (the content of misc changes is not displayed). |
|
|
|
|
|
|
|
|
|
For example, a fix for a bug reported in #1234 would have its |
|
|
|
|
changelog entry in ``changelog.d/1234.bugfix``, and contain content |
|
|
|
|
like "The security levels of Florbs are now validated when |
|
|
|
|
recieved over federation. Contributed by Jane Matrix". |
|
|
|
|
|
|
|
|
|
Attribution |
|
|
|
|
~~~~~~~~~~~ |
|
|
|
|
|
|
|
|
|