Enable GitHub to render ChangeLog as Markdown#2899
Merged
ann0see merged 1 commit intojamulussoftware:masterfrom Oct 7, 2022
Merged
Enable GitHub to render ChangeLog as Markdown#2899ann0see merged 1 commit intojamulussoftware:masterfrom
ann0see merged 1 commit intojamulussoftware:masterfrom
Conversation
This enables rendering of the ChangeLog as markdown file on GitHub. See: github/markup#1069 (comment)
hoffie
approved these changes
Oct 6, 2022
Member
hoffie
left a comment
hoffie
left a comment
There was a problem hiding this comment.
Nice!
Preview looks good: https://github.com/ann0see/jamulus/blob/ConvertChangeLog/ChangeLog
pljones
approved these changes
Oct 7, 2022
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This enables rendering of the ChangeLog as markdown file on GitHub. See: github/markup#1069 (comment)
Short description of changes
GitHub from now on will enable markdown rendering of the ChangeLog. This also allows direct links to Versions which might get handy in release announcements.
CHANGELOG: SKIP
Context: Fixes an issue?
No. But it has been discussed somewhere in another context (especially releated to renaming the ChangeLog to ChangeLog.md which is now no longer needed.)
Does this change need documentation? What needs to be documented and how?
Probably not
Status of this Pull Request
Ready to be merged.
What is missing until this pull request can be merged?
/
Checklist