Repository navigation
docs: clarify naming modes and publication requirements - #2
Merged
Merged
Conversation
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 README now introduces both actual filename changes and display-only names, uses the real
treldefault, and states the tested platform scope alongside the release notes. Automation introductions and the bug-report version example are refreshed.The release guide now explicitly requires merging reviewed source into
mainand matching its manifest, the version tag, and the release asset manifest.Validation: checked relative Markdown links and code fences, ran
git diff --check, and confirmed product code, workflows, version metadata, and installation files are unchanged from 0.7.0.