Repository navigation
Restore automated releases and bump to v2.0.0 - #18
Merged
Merged
Conversation
Release workflow (removed with the other workflows in the standalone restore) now reads VERSION: when a push to main changes it and the tag v<VERSION> does not exist, it creates the tag and a GitHub release with generated notes. 2.0.0 marks merging the homepage into this repository and moving every URL under /<en|ko>/.
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
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.
Summary
VERSION: when a push tomainchangesVERSIONandv<VERSION>is not tagged yet, it creates the tag and a GitHub release with generated notes.workflow_dispatchcan rerun it.VERSION1.2.0 → 2.0.0: Build jmnote.com from this repository with /<lang>/ paths #17 merged the homepage into this repository and moved every URL under/<en|ko>/. 1.2.0 was never tagged, so it is skipped.Test plan
v2.0.0with notes