Repository navigation
Move docs and CI to main-only branching with a version bump per PR - #46
Merged
rickdijk merged 1 commit intoSep 23, 2026
Conversation
Prepares octo_image for the main-only branching model already used by flutter_cache_manager and flutter_cached_network_image (FPL-29). main is not yet the default branch or protected; that happens as a follow-up settings change once this PR is merged and CI is green against main. - build.yaml: trigger on push/pull_request against main instead of develop - AGENTS.md, CONTRIBUTING.md: branch from and target main, add the per-PR version bump and CHANGELOG entry step (skipped for docs-only and CI-only changes, as this PR is), update the Releases section to tagging-only with no release-prep PR - PULL_REQUEST_TEMPLATE.md: rebase item now says main, add the version-bump checklist item - README.md: pin the demo GIF to the v2.1.0 tag instead of develop, so the link survives the branch move Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
rickdijk
deleted the
rick/fpl-29-octo_image-move-to-main-only-branching-with-a-version-bump
branch
September 23, 2026 18:15
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.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
CI and documentation change: moves octo_image onto the main-only branching model already used by flutter_cache_manager and flutter_cached_network_image.
developis the default branch and the branch of record.build.yamltriggers ondevelop.AGENTS.md,CONTRIBUTING.mdand the PR template all point contributors atdevelop, and nothing enforces a version bump per PR. The README demo GIF is loaded fromdevelop.🆕 What is the new behavior (if this is a feature change)?
build.yamltriggers onmaininstead ofdevelop.AGENTS.mdandCONTRIBUTING.mddescribemainas the branch of record, withdevelopandmastergone and a ruleset blockingdevelop's re-creation. Both documents, and the PR template, now require apubspec.yamlversion bump and a datedCHANGELOG.mdentry on every PR, except docs-only and CI-only ones (this one included, so it doesn't bump).AGENTS.md's Releases section changes to tagging the merge commit directly, with no separate release-prep PR. The README GIF is pinned to thev2.1.0tag instead ofdevelop, so the link survives the branch move.This PR only changes docs and CI config;
maindoes not become the default or protected branch until a follow-up settings change once this is merged and green.💥 Does this PR introduce a breaking change?
No.
🐛 Recommendations for testing
dart format --set-exit-if-changed .,flutter analyzeandflutter testall pass locally with no code changes. Sincebuild.yaml'spull_requesttrigger now filters onmainand this PR targetsdevelop, CI won't fire on the PR automatically; it was run viaworkflow_dispatchon this branch instead.📝 Links to relevant issues/docs
FPL-29
🤔 Checklist before submitting
🤖 Generated with Claude Code