nucypher/newsfragments
Bogdan Opanchuk 663ba45e19 Newsfragment for PR #2498 2021-01-05 15:46:39 -08:00
..
.gitignore Initial setup for towncrier 2020-05-28 11:59:08 -07:00
2440.misc.rst Newsfragment for PR 2440 2021-01-04 09:20:00 +01:00
2477.doc.rst Script that compiles contracts and transforms userdoc+devdoc to rst 2020-12-25 11:26:51 +03:00
2489.bugfix.rst Fix rtd build 2020-12-31 14:36:29 +03:00
2491.bugfix.rst newsfragment for PR #2491 2021-01-02 17:19:13 -08:00
2492.bugfix.rst Added solidity installation step to sphinx and rtd build 2021-01-04 11:55:44 +03:00
2498.bugfix.rst Newsfragment for PR #2498 2021-01-05 15:46:39 -08:00
README.md Additional clarification about optional use of issue newsfragment files. 2020-11-03 14:49:57 -05:00
validate_files.py Add missing lisences 2020-09-08 13:08:10 -07:00

README.md

This directory collects "newsfragments": short files that each contain a snippet of ReST-formatted text that will be added to the next release notes. This should be a description of aspects of the change (if any) that are relevant to users. (This contrasts with the commit message and PR description, which are a description of the change as relevant to people working on the code itself.)

The pull request (PR) number should be used for the newsfragment file. Each file should be named <PR_NUMBER>.<TYPE>.rst, where <TYPE> is one of:

  • feature
  • bugfix
  • doc
  • misc

For example: 123.feature.rst, 456.bugfix.rst

Along with the required PR newsfragment file (enforced by a GitHub Action), additional newsfragment files for issues linked to the PR can optionally be included by following the same naming convention above, and using <ISSUE_NUMBER> instead of <PR_NUMBER>.

Note that the towncrier tool will automatically reflow your text, so don't try to do any fancy formatting. Run towncrier --draft to get a preview of what the release notes entry will look like in the final release notes.