74df16e015
- Use random uuid4 as id for request - Improve error handling in case code/message isn't available. - Add to headers dictionary instead of recreating - offchain -> off-chain |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| 3500.feature.rst | ||
| 3511.feature.rst | ||
| 3523.dev.rst | ||
| 3535.dev.rst | ||
| 3538.feature.rst | ||
| 3539.dev.rst | ||
| 3545.dev.rst | ||
| 3547.dev.rst | ||
| 3553.dev.rst | ||
| 3554.dev.rst | ||
| 3556.dev.rst | ||
| 3557.dev.rst | ||
| 3558.feature.rst | ||
| 3560.feature.rst | ||
| 3562.feature.rst | ||
| 3563.dev.rst | ||
| 3564.dev.rst | ||
| 3569.feature.rst | ||
| 3571.feature.rst | ||
| README.md | ||
| validate_files.py | ||
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. It contrasts with the commit message and PR description, which are descriptions of the change relevant to people working on the code itself.
The pull request (PR) number should be included in the newsfragment file name. Each newsfragment file
should be named <PR_NUMBER>.<TYPE>.rst, where <TYPE> is one of:
feature- featuresbugfix- bugfixesdoc- documentationremoval- deprecations and removalsmisc- otherdev- internal development tasks
For example: 123.feature.rst, 456.bugfix.rst, 789.doc.rst.
There can be multiple newsfragment files of different types for the same PR
e.g. 123.feature.rst and 123.removal.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 preview what the release notes entry
will look like in the final release notes.