Move to a main-only branching model - #529
Merged
Merged
Conversation
Aligns this repo with Baseflow's other repositories (flutter-permission-handler): main is the only long-lived branch and all PRs target it directly. Points CI triggers, contributor docs and the PR template at main, and documents the branch policy and the tag-driven release process in AGENTS.md so it holds for future work. Also drops the branch name from the published homepage URL and fixes the codecov badge, both of which referenced branches that no longer apply. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Repository workflow change (CI config + docs), aligning with Baseflow's other repositories.
The repo runs a two-branch model:
developis the default and integration branch,mainlags behind and is fast-forwarded at release time. CI triggers,CONTRIBUTING.md,AGENTS.mdand the PR template all point contributors atdevelop. The core package'shomepageembeds/tree/develop/, and the README's codecov badge points at amasterbranch that no longer exists.🆕 What is the new behavior (if this is a feature change)?
mainis the only long-lived branch and all PRs target it directly. CI triggers, contributor docs and the PR template referencemain, andAGENTS.mdstates the branch policy as a hard requirement. The publishedhomepagenow points at the repository root so it can't break when a branch goes away, and the codecov badge points atmain.AGENTS.mdalso gains a Releases section documenting the existing tag-driven publish flow (tag onmain; the tag push is what triggers pub.dev publishing via OIDC), which until now was undocumented.The GitHub-side changes that accompany this — default branch, squash-only merges, branch protection on
main, retargeting open PRs, and retiringdevelop— are applied separately in repository settings.💥 Does this PR introduce a breaking change?
No.
🐛 Recommendations for testing
Confirm this PR's own checks run, which verifies the
pull_request: branches: [main]trigger works.dart format --set-exit-if-changed .andflutter analyzepass locally for the core package; no Dart source changed.📝 Links to relevant issues/docs
Matches the model used by flutter-permission-handler.
🤔 Checklist before submitting
🤖 Generated with Claude Code