Repository navigation
chore: make main the branch the contract describes - #52
Merged
Merged
Conversation
Every pull request since 17 September has been opened against `main` and merged there, and `dev` has not moved since 15 September — by the time v0.9.1 was tagged it was thirty-five commits behind. The documents still described the opposite: CONTRIBUTING and the pull request template told contributors to retarget onto `dev`, and a workflow commented on every PR to say the base was wrong when it was in fact the one being used. With one person merging and a tag per release, the second branch never bought anything. It carried the same commits a day later, and the only thing it produced was a bot arguing with the actual workflow on every pull request. So `main` is the contract now: PRs open against it, releases are tags on it. The retarget workflow is gone, CI no longer watches a branch that does not exist, and the pull request template says the pre-filled base is the right one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Thanks for the PR. One thing before review: this targets
No need to close and reopen: click Edit next to the PR title and change the base branch to See CONTRIBUTING.md and CONTRIBUTING.md for the branch contract. |
Merged
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.
Every pull request since 17 September has been opened against
mainand mergedthere, and
devhas not moved since 15 September — by the time v0.9.1 wastagged it was thirty-five commits behind. The documents still described the
opposite:
CONTRIBUTING.mdand the pull request template told contributors toretarget onto
dev, andpr-base-guard.ymlcommented on every PR to say thebase was wrong when it was in fact the one being used.
With one person merging and a tag per release, the second branch never bought
anything: it carried the same commits a day later, and the only thing it
produced was a bot arguing with the actual workflow on every pull request.
CONTRIBUTING.md: PRs open againstmain; says what happened todev..github/PULL_REQUEST_TEMPLATE.md: the pre-filled base is the right one..github/workflows/pr-base-guard.yml: deleted..github/workflows/ci.yml: stops watching pushes to a branch that is goingaway.
The
devbranch itself is deleted separately. Its two commits are thepre-squash originals of #15 and #16, both already on
main.🤖 Generated with Claude Code