Use Markdown link references #602
Replies: 2 comments 3 replies
-
Hmm, there is currently no method of adding a changelog footer like there is for headers. Nor would the header even include the data you would need to build this. It is an interesting idea and actually brings up some confusing parts of the config as I was looking around. The key of header is used in many places in similar but slightly different ways. I'm going to take a little time to see if I can fix the inconsistencies and include the option to support this feature. Can't say when though, but I do like the idea. |
Beta Was this translation helpful? Give feedback.
-
Could also make sense to allow them at the end of a specific version. E.g. ## [1.0.1] - 2019-08-24
### Added
- A shiny new feature ([#456])
### Fixed
- Prevent segmentation fault upon `close()` ([#123])
[#123]: https://github.com/owner/name/pulls/123
[#456]: https://github.com/owner/name/pulls/456
## [1.0.0] - 2019-08-23
_Initial release._
[1.0.1]: https://github.com/owner/name/releases/tag/v1.0.1
[1.0.0]: https://github.com/owner/name/releases/tag/v1.0.0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be nice to be able to use Markdown link references to keep the unrendered Markdown form of the changelog readable. This is recommended for example when following Keep a Changelog or Common Changelog formats.
For example:
Beta Was this translation helpful? Give feedback.
All reactions