You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,13 @@ Read @FORK.md for full context on this fork.
4
4
5
5
## Branch & Commit Strategy
6
6
7
-
-`af-main` is the fork branch. It must always be exactly **one commit** ahead of upstream.
8
-
- That commit has the subject line: `feat: AppFolio spec-kit fork — specify-af-cli with bundled extensions`. Use this to identify it.
9
-
- When merging work into `af-main` (directly or via squash merge), amend into this single fork commit rather than adding new commits.
7
+
-`af-main` is the fork branch. It accumulates commits from PRs and releases.
10
8
- On feature branches, squash to one commit before merge.
11
-
- Before integrating an upstream release, ensure af-main is one commit ahead, then merge the upstream tag. Resolve conflicts per @FORK.md.
9
+
- Before integrating an upstream release, squash all af-main commits since the fork baseline (see @FORK.md) into one commit, then merge the upstream tag. Resolve conflicts per @FORK.md.
12
10
- Use Conventional Commits on feature branches: `feat:`, `fix:`, `chore:`, etc.
13
11
14
12
## Git Rules (enforced by Claude unless user explicitly overrides)
15
13
16
-
-**Never create additional commits on `af-main`** — always amend the single fork commit.
17
14
-**Always work on a feature branch.** Never commit directly to `af-main` without user confirmation.
18
15
-**Never push merge commits.** If a pull or merge introduces a merge commit, rebase instead.
19
16
-**Before force-pushing `af-main`:** confirm with the user first — this rewrites shared history.
0 commit comments