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
{{ message }}
Repository navigation
Commit b5f041d
Browse filesBrowse the repository at this point in the historyBrowse files
docs: align agent branch policy with Go port endgame
Replace dual-track landing guesses with owner intake rules: dev2-go as home base, dev allowed only with dev2-go coverage before merge, planned FF collapse.
Copy file name to clipboardExpand all lines: AGENTS.md
+36-30Lines changed: 36 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,45 +40,48 @@ Read the nearest nested `AGENTS.md` before changing files in a scoped directory.
40
40
41
41
## Branch targets
42
42
43
-
-**`dev`**
44
-
- Purpose: Default integration branch.
45
-
- Pull-request rule: All normal changes target `dev`.
43
+
Interim Go-port endgame (owner direction). `MAINTAINERS.md` is authoritative.
46
44
47
45
-**`dev2-go`**
48
-
- Purpose: Parallel Go native-port integration line.
49
-
- Pull-request rule: Use only when the primary purpose is Go native-port work and the change touches `go/`, `bin/native-runtime.mjs`, `src/lib/runtime-entry.ts`, or Go release-asset tooling.
46
+
- Purpose: Current home base for dogfooding, triage, and most product work.
47
+
Strict superset of `dev` (has TS **and**`go/`).
48
+
- Pull-request rule: Features, behavior changes, and anything that must keep
49
+
TS + Go in sync target `dev2-go` (one PR). Prefer this for open product PRs.
50
+
51
+
-**`dev`**
52
+
- Purpose: Current release-path integration line (still TS toward `main` /
53
+
`latest` until Go graduates through `preview`).
54
+
- Pull-request rule: `dev` PRs are allowed, but **do not merge** until the
55
+
same change is also on `dev2-go` (rebase/retarget there and/or add the Go
56
+
side). Urgent “latest is on fire” hotfixes may land on `dev` first with
57
+
`needs-go-port`, then follow up on `dev2-go`. Tiny non-behavior work
58
+
(docs / CI / governance) may stay on `dev`.
50
59
51
60
-**`main`**
52
-
- Purpose: Release branch.
53
-
- Pull-request rule: Maintainer-controlled promotion from `dev` only. Do not target feature pull requests here.
61
+
- Purpose: Release branch (`latest`).
62
+
- Pull-request rule: Maintainer-controlled promotion from `dev` only. Do not
63
+
target feature pull requests here. After `dev` is fast-forwarded to
64
+
include Go, do not promote `dev` → `main` until preview has baked (freeze
65
+
lands with that fast-forward).
54
66
55
67
-**`preview`**
56
-
- Purpose: Prerelease train.
57
-
- Pull-request rule: Maintainer-directed prerelease work only.
68
+
- Purpose: Prerelease train (`preview` dist-tag) for baking Go before `latest`.
69
+
- Pull-request rule: Maintainer-directed prerelease work only. Prefer
70
+
merge/ff only — do not force-push.
58
71
59
72
A pull request targeting neither `dev` nor `dev2-go` is invalid unless it is a
60
-
maintainer-controlled release or promotion. A pull request targeting `dev2-go`
61
-
without the required Go/native scope must be retargeted to `dev`.
62
-
63
-
### Interim dual-track intent (`dev` and `dev2-go`)
64
-
65
-
The Go port is still stabilizing, so the project is moving toward **two release
66
-
tracks** rather than one shared line:
67
-
68
-
-`dev` — TypeScript / Bun track (current release path to `main`)
69
-
-`dev2-go` — Go track (may gain its own separate release path; still contains
70
-
shared TypeScript surfaces today)
73
+
maintainer-controlled release or promotion. Do **not** open duplicate PRs for
74
+
the same change on both lines; maintainers sync by rebasing `dev2-go` onto
75
+
`dev`. Contributors never stack the same commits twice.
71
76
72
-
Owner direction for handling issues and PRs: keep both tracks in mind, and
73
-
prefer landing work on **both**`dev` and `dev2-go` when the change belongs on
74
-
both, until a pipeline or separate Go release path is decided. Exact mechanics
75
-
(which base first, cherry-pick vs paired PR, whether `dev2-go` ships alone) are
76
-
still being decided — do not invent dual-base PRs, and do not treat the old
77
-
“`dev2-go` = Go-only work” rule as the whole story anymore.
77
+
### Endgame (planned)
78
78
79
-
Prefer promoting and deploying release-path work within about a week when
80
-
maintainers direct it. `MAINTAINERS.md` is authoritative; update it when the
81
-
owner finalizes the pipeline / separate-release decision.
79
+
1. Fast-forward `dev` to `dev2-go`, then retire `dev2-go` as an intake target
0 commit comments