Skip to content

Land agent work on beta; main moves only when Jon asks - #1862

Merged
Noisemaker111 merged 1 commit into
betafrom
claude/land-on-beta-q4m8t2
Sep 27, 2026
Merged

Noisemaker111 merged 1 commit into
betafrom
claude/land-on-beta-q4m8t2

Conversation

@Noisemaker111

Copy link
Copy Markdown
Owner

The agents branch was renamed to beta (Jon, 2026-09-27: "lets actually make it beta for everything and allow agents push"). This moves the landing-branch policy and tooling with it.

  • AGENTS.md: task branches start from origin/beta; work lands on beta by pushing verified commits directly or by merging the PR into beta yourself (gh pr merge <n> --auto --merge, or --merge if that errors for any reason but a failing check) and confirming MERGED. main is the stable branch and moves only when Jon asks.
  • agent:worktree and ship:preflight fetch, branch from and diff against origin/beta; preflight refuses shipping from main/beta directly.
  • workflow skill and the session-start merge policy say the same.

Verified on c28dfd5 (temp HOME/USERPROFILE):

  • bun run agent:bootstrap then bun run ship:preflight → ship preflight ok
  • bun run agent:worktree -- beta-probe-x3k8m1 → from origin/beta (55a2f410), base: origin/beta, bootstrapped; probe worktree removed afterwards
  • bun .claude/hooks/session-start.mjs → prints the new beta merge policy, default: beta
  • bun run check-skills → ok

🤖 Generated with Claude Code

The agents branch was renamed to beta. Task branches start from origin/beta,
and agents land work there themselves: push verified commits to beta or merge
their PR into beta (gh pr merge --auto --merge, or --merge if that errors for
any reason but a failing check) and confirm MERGED. agent:worktree and
ship:preflight branch from and compare against origin/beta, and the
session-start merge policy says the same.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Noisemaker111
Noisemaker111 merged commit 458d27c into beta Sep 27, 2026
6 checks passed
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