Track release notes in Git #8827
Merged
Conversation
This file contains 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
github-actions
bot
added
the
docs
ExE-Boss
approved these changes
Jan 22, 2021
Elchi3
approved these changes
Feb 17, 2021
|
@Elchi3 I added the latest releases. Also, I uppercased the file name, to line up with the other top-level directory documentation. Is that OK? |
|
That's okay with me. Thanks! Merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR scrapes BCD's existing GitHub release notes into the repo. This is a first step toward #6759 and being able to collaborate on release notes as a routine matter for BCD.
To do this, I wrote a very ugly script that got the release details from the GitHub API and wrote out some sensible-looking Markdown. I expect that this is a one-time effort, so I didn't clean up the script and include it in this PR. I also applied a couple of other one-time cleanups:
#1234) into proper Markdown links (e.g.,[#1234](https://github.com/mdn/browser-compat-data/issues/1234))https://github.com/mdn/browser-compat-data/compare/v3.0.3...v3.0.4, which becomes a link with the textv3.0.3...v3.0.4) into Markdown (such as[`v3.0.3...v3.0.4`](https://github.com/mdn/browser-compat-data/compare/v3.0.3...v3.0.4))