Restore main as the bleeding-edge branch - #151
Merged
Merged
Conversation
|
lorisleiva
force-pushed
the
chore/restore-main-config
branch
from
August 27, 2026 15:10
21a722c to
1f18870
Compare
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.
This PR follows the branch rename back to
main, reverting the mainless experiment in favour of a permanentmainbranch:.changeset/config.jsonpoints back atmainand the workflow triggers acceptmainalongside the numeric major-branch pattern. It also adds the repository's missingCONTRIBUTING.md, documenting the day-to-day flow and linking the ecosystem-wide release process.