@@ -16,20 +16,20 @@ through GitHub repository settings.
1616
1717## Review and merge policy
1818
19- - Pull requests target ` dev ` by default . ` dev2-go ` is a parallel integration
20- line for Go native-port work. Each pull request still has one base; the
21- target-branch check accepts both as integration targets. It cannot
22- distinguish scoped Go port work from anything else aimed at ` dev2-go ` , so
23- that boundary is enforced in review: redirect an out-of-scope pull request to
24- ` dev ` rather than treating the automation's silence as approval.
25- - ** Dual landing: ** while both ` dev ` and ` dev2-go ` remain active, work that
26- belongs on both lines must land on both after merge (cherry-pick, paired
27- follow-up PR, or maintainer sync). Do not treat a single-base merge as done
28- if the other line still needs the change. Automated dual-landing may replace
29- this manual step once the owner ships the pipeline; until then, dual landing
30- is expected when handling issues and PRs .
31- - Promotion to ` main ` and npm releases remain maintainer-controlled and still
32- happen only from ` dev ` . Prefer promoting and deploying release-path merges
19+ - Pull requests still use ** one ** GitHub base per PR . ` dev ` remains the default
20+ TypeScript / Bun integration line and the current path to ` main ` . ` dev2-go `
21+ is the Go track; it also carries shared TypeScript today. The target-branch
22+ check accepts both bases.
23+ - ** Interim dual-track intent: ** the Go port is still finding instability, so
24+ the owner wants two release tracks and is still deciding whether ` dev2-go `
25+ can ship separately. Until that is finalized (and until any sync pipeline
26+ lands), when handling issues or PRs prefer getting the same change onto
27+ ** both ** ` dev ` and ` dev2-go ` when it belongs on both (cherry-pick, paired PR,
28+ or maintainer sync). Do not treat “merged to one track only” as finished if
29+ the other track still needs it. Do not hard-code a finished workflow beyond
30+ what the owner has confirmed .
31+ - Promotion to ` main ` and npm releases remain maintainer-controlled from ` dev `
32+ until a separate Go release path exists . Prefer promoting and deploying
3333 within about a week when the owner or maintainers direct it.
3434- A pull request requires approval from at least one maintainer and successful required CI checks
3535 before merge.
0 commit comments