Unverified Commit 0164e3cf authored by Francesco Gazzetta's avatar Francesco Gazzetta Committed by GitHub
Browse files

Merge pull request #7257 from fgaz/changelog.d-docs

Add changelog.d documentation
parents 0369f8b8 64411112
......@@ -3,7 +3,7 @@
Please include the following checklist in your PR:
* [ ] Patches conform to the [coding conventions](https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#conventions).
* [ ] Any changes that could be relevant to users have been recorded in the changelog (add file to `changelog.d` directory).
* [ ] Any changes that could be relevant to users [have been recorded in the changelog](https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#changelog).
* [ ] The documentation has been updated, if necessary.
Please also shortly describe how you tested your change. Bonus points for added tests!
......@@ -221,6 +221,48 @@ We like [this style guide][guide].
[guide]: https://github.com/tibbe/haskell-style-guide/blob/master/haskell-style.md
When opening a pull request, you should write a changelog entry.
This is done by adding a file in the `changelog.d` directory.
The files follow a simple key-value format similar to the one for .cabal files.
Here's an exhaustive example:
synopsis: Add feature xyz
packages: cabal-install
prs: #0000
issues: #0000 #0000
significance: significant
description: {
- Detail number 1
- Detail number 2
Only the `synopsis` field is actually required, but you should also set the others where applicable.
| Field | Description |
| ----- | ----------- |
| `synopsis` | Brief description of the change. Often just the pr title. |
| `description` | Longer description, with a list of sub-changes. Not needed for small/atomic changes. |
| `packages` | Packages affected by the change (`cabal-install`, `Cabal`...). Omit if it's an overarching or non-package change. |
| `prs` | Space-separated hash-prefixed pull request numbers containing the change (usually just one). |
| `issues` | Space-separated hash-prefixed issue numbers that the change fixes/closes/affects. |
| `significance` | Set to `significant` if the change is significant, that is if it warrants being put near the top of the changelog. |
You can find a large number of real-world examples of changelog files
At release time, the entries will be merged with
[this tool](https://github.com/phadej/changelog-d).
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment