Skip to content

docs: document branch setup workflow#302

Merged
lewtun merged 1 commit into
mainfrom
codex/document-branch-setup-workflow
Jun 7, 2026
Merged

docs: document branch setup workflow#302
lewtun merged 1 commit into
mainfrom
codex/document-branch-setup-workflow

Conversation

@lewtun
Copy link
Copy Markdown
Member

@lewtun lewtun commented Jun 7, 2026

Summary: Adds a Git workflow note requiring new branches and worktrees to start after pulling latest main. Tests: uv run ruff check ., uv run ruff format --check .

Co-authored-by: OpenAI Codex <codex@openai.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 7, 2026

Claude finished @lewtun's task in 37s —— View job


PR Review: docs: document branch setup workflow

No blocking issues — LGTM

  • Read the diff and surrounding AGENTS.md context
  • Assess correctness, consistency, and style fit

This is a documentation-only change: it adds a ## Git Workflow section to AGENTS.md:23-25 advising that new branches/worktrees start from an up-to-date main. No code, routing, auth, or test surface is touched, so the review focus areas (correctness/security/LiteLLM routing/agent loop/test coverage) don't apply here.

The addition is well-placed (between Development Checks and GitHub CLI), matches the existing heading + bullet style, and the guidance is sound. The ## Hugging Face Space Deploys block at AGENTS.md:46 already opens with git pull --ff-only origin main, so the new note is consistent with the rest of the file.

P2 (informational, optional): the new bullet says to switch to main and pull the latest changes but doesn't specify the fast-forward-only form used elsewhere in this file (git pull --ff-only origin main, AGENTS.md:46). Aligning the wording would keep the guidance uniform — non-blocking.

Nothing to fix. Ship it.

@lewtun lewtun merged commit 43f9cb0 into main Jun 7, 2026
3 checks passed
@lewtun lewtun deleted the codex/document-branch-setup-workflow branch June 7, 2026 20:37
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