From a0e6f0fcba479d34615014c818edb24d72fac9d4 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Fri, 5 Jun 2026 11:06:30 +0200 Subject: [PATCH] document the commit-directly-to-main workflow Record that this solo-dev repo lands routine work straight on main and does not use a branch-first flow, so the generic assistant default of branching before committing on the default branch does not apply here. Co-Authored-By: Claude --- CLAUDE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index d111ba38..f49b5b2f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -76,6 +76,10 @@ make clean # remove build artefacts One-time setup on a fresh clone: `make hooks && flutter pub get` once Flutter is installed. +## Git workflow + +Commit and push directly to `main` for routine work — this is a solo-dev repo and does not use a branch-first / feature-branch flow. Do **not** create a working branch just to land a change. (This overrides the generic "branch before committing on the default branch" assistant default.) The usual safety rules still hold: never `--no-verify`, never force-push `main`, and let the pre-push gate run. + ## Changelog discipline [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/). Every user-visible commit adds an entry under `## [Unreleased]` in [`CHANGELOG.md`](CHANGELOG.md). Cutting a release means moving Unreleased entries under a new dated version heading **and** bumping `pubspec.yaml` `version:` in the same commit — see [`.claude/skills/git-commit/SKILL.md`](.claude/skills/git-commit/SKILL.md) for the full rule.