Repository navigation
docs: use main as the only branch after 1.0 - #363
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
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.
After 1.0,
mainis the only branch. This PR changes the repo to match:AGENTS.md,CONTRIBUTING.md, the root README and the PR template say to open PRs againstmain.ci.ymlandrelease.ymlrun on a push tomainonly.main.releasing-packagesskill no longer has the section "Movemainto a stable release", because it applies only to two branches. The GitHub environmentnpmallows onlymain.release-please-config.jsonno longer hasrelease-as, as the skill says to do after a release.Merge this PR into
nextonly after release PR #360 merges and its publish job succeeds. Before that, the merge stops the release:release.ymlwould no longer run onnext, and #360 needsrelease-as.After the merge, reset
maintonext.mainthen contains this PR, so no retarget is necessary. A failed publish can still be re-run, because a re-run uses the workflow file of the release commit.Then do these steps as the owner:
mainthe default branch.nextfrom the deployment branches of the GitHub environmentnpm.nextfrom the target branches of the ruleset "Require CI".nextbranch.Test plan
pnpm format:checkandpnpm lintpass.