Skip to content

Remove PR approval gate from CLAUDE.md workflow #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
juhgiyo merged 1 commit into from
Mar 27, 2026
Merged

Remove PR approval gate from CLAUDE.md workflow #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading