Repository navigation
docs: describe releases for repositories with dev and main - #280
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 org CONTRIBUTING guide keeps the universal rules under
## Commits(squash-merged under the PR title in Conventional Commits form, the## Release notesection, Renovate's scopes,sec:, breaking changes) and moves the release table and the never-release list under a section scoped to repositories whose default branch isdev, since those are the only ones that release. The README line and one Renovate preset description match it.Tested: the org-default docs scan passes at 497 of 500 words; the
## Reviewparagraphs are unchanged;default.jsonparses.