From 59208e6c7240821b4dd13320cfb1f328fcf58e7a Mon Sep 17 00:00:00 2001 From: Chris La Date: Fri, 27 Mar 2026 16:39:11 -0700 Subject: [PATCH] Remove PR approval gate from CLAUDE.md workflow Co-Authored-By: Claude Opus 4.6 (1M context) --- CLAUDE.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 06f129b..fbe5088 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -8,10 +8,7 @@ ## After completing any code change -1. Show me the full `git diff` for review -2. Wait for my explicit approval before proceeding -3. Once approved: - - Rebase from `main` before committing (`git fetch origin && git rebase origin/main`) - - **If the current branch has an open PR**, push to that branch to update the existing PR. - - **If the current branch's PR is already merged** (or there is no PR), pull the latest `main` (`git checkout main && git pull origin main`), then create a fresh branch from `main` and open a new PR. - - Never reuse a branch whose PR has been merged. Each merged PR keeps its own branch. +1. Rebase from `main` before committing (`git fetch origin && git rebase origin/main`) +2. **If the current branch has an open PR**, push to that branch to update the existing PR. +3. **If the current branch's PR is already merged** (or there is no PR), pull the latest `main` (`git checkout main && git pull origin main`), then create a fresh branch from `main` and open a new PR. +4. Never reuse a branch whose PR has been merged. Each merged PR keeps its own branch.