Skip to content

Move docs and CI to main-only branching with a version bump per PR - #46

Merged
rickdijk merged 1 commit into
developfrom
rick/fpl-29-octo_image-move-to-main-only-branching-with-a-version-bump
Sep 23, 2026
Merged

rickdijk merged 1 commit into
developfrom
rick/fpl-29-octo_image-move-to-main-only-branching-with-a-version-bump

Conversation

@rickdijk

Copy link
Copy Markdown
Collaborator

✨ 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.

⤵️ What is the current behavior?

develop is the default branch and the branch of record. build.yaml triggers on develop. AGENTS.md, CONTRIBUTING.md and the PR template all point contributors at develop, and nothing enforces a version bump per PR. The README demo GIF is loaded from develop.

🆕 What is the new behavior (if this is a feature change)?

build.yaml triggers on main instead of develop. AGENTS.md and CONTRIBUTING.md describe main as the branch of record, with develop and master gone and a ruleset blocking develop's re-creation. Both documents, and the PR template, now require a pubspec.yaml version bump and a dated CHANGELOG.md entry 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 the v2.1.0 tag instead of develop, so the link survives the branch move.

This PR only changes docs and CI config; main does 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 analyze and flutter test all pass locally with no code changes. Since build.yaml's pull_request trigger now filters on main and this PR targets develop, CI won't fire on the PR automatically; it was run via workflow_dispatch on this branch instead.

📝 Links to relevant issues/docs

FPL-29

🤔 Checklist before submitting

  • All projects build
  • Follows style guide lines
  • Relevant documentation was updated
  • Rebased onto current main
  • Version bumped in pubspec.yaml and dated CHANGELOG.md entry added (skip for docs-only and CI-only changes)

🤖 Generated with Claude Code

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
rickdijk merged commit 0c8c854 into develop Sep 23, 2026
10 checks passed
@rickdijk
rickdijk deleted the rick/fpl-29-octo_image-move-to-main-only-branching-with-a-version-bump branch September 23, 2026 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant