Repository navigation
ci(release): publish the repository readme on npm - #1
Merged
Merged
Conversation
The npm page showed a stale 'Coming soon' README. The release now writes README.md into the npm package with its relative links and images pointing at the release tag on GitHub, and a test checks that every link in it works from npm.
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
1 participant
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.
The npm page for
skillpouchshowed an old 10-line README ("Coming soon").scripts/release.mjs stampnow copies the rootREADME.mdintonpm/skillpouch, rewriting relative links: images toraw.githubusercontent.com/…/v<version>/…, files and folders togithub.com/…/blob/v<version>/….npm/skillpouch/README.mdis removed and ignored; it's generated at release.ci:doesn't release by itself; the npm page updates with the nextfix/featrelease.