Repository navigation
Docs: versions of the documentation by mike - #47
Merged
Merged
Conversation
…atest from the release tags Signed-off-by: Dmitriy Aleksandrov <goodmobiledevices@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #47 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 30 30
Lines 2571 2571
=========================================
Hits 2571 2571 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Benchmark diff:
|
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.
The site showed only
main, while the users are on the released versions.gh-pagesbranch, the workflow publishes this branch by GitHub Pages Actions as before, so the settings of Pages stay the same.mainupdates thedevversion; a tagvX.Y.Zpublishes the versionX.Ywith thelatestalias and makes it the default. Until the first such releaselatestisdev, so the links work at once./latest/.The sequence (main, release, main, patch release, next minor release) is checked locally on a copy of the repository. The pages of the current site without the version in the path (
/tinyconf/use-cases/) will be 404 after the switch; the site is new, the Readme links are updated.