diff --git a/.claude/commands/release/check-out-pr.md b/.claude/commands/release/check-out-pr.md deleted file mode 100644 index 23e95e3e..00000000 --- a/.claude/commands/release/check-out-pr.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: Review a PR in a new worktree -allowed-tools: Bash(git worktree:*), Bash(gh pr:*), Bash(git branch:*) ---- - -Check out a GitHub pull request for review. - -## Usage - -``` -/check-out-pr -``` - -## What to do - -1. If no PR number is provided, list all open pull requests and ask the user to select one -2. Get PR information using `gh pr view --json number,headRefName` -3. **Ask the user** whether they want to: - - **A) Check out in current directory** — simple `gh pr checkout ` - - **B) Create a new worktree** — isolated copy at `../yaak-worktrees/pr-` -4. Follow the appropriate path below - -## Option A: Check out in current directory - -1. Run `gh pr checkout ` -2. Inform the user which branch they're now on - -## Option B: Create a new worktree - -1. Create a new worktree at `../yaak-worktrees/pr-` using `git worktree add` with a timeout of at least 300000ms (5 minutes) since the post-checkout hook runs a bootstrap script -2. Checkout the PR branch in the new worktree using `gh pr checkout ` -3. The post-checkout hook will automatically: - - Create `.env.local` with unique ports - - Copy editor config folders - - Run `npm install && npm run bootstrap` -4. Inform the user: - - Where the worktree was created - - What ports were assigned - - How to access it (cd command) - - How to run the dev server - - How to remove the worktree when done - -### Example worktree output - -``` -Created worktree for PR #123 at ../yaak-worktrees/pr-123 -Branch: feature-auth -Ports: Vite (1421), MCP (64344) - -To start working: - cd ../yaak-worktrees/pr-123 - npm run app-dev - -To remove when done: - git worktree remove ../yaak-worktrees/pr-123 -``` - -## Error Handling - -- If the PR doesn't exist, show a helpful error -- If the worktree already exists, inform the user and ask if they want to remove and recreate it -- If `gh` CLI is not available, inform the user to install it diff --git a/.codex/skills/release-check-out-pr/SKILL.md b/.codex/skills/release-check-out-pr/SKILL.md deleted file mode 100644 index 88755e0e..00000000 --- a/.codex/skills/release-check-out-pr/SKILL.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -name: release-check-out-pr -description: Check out a GitHub pull request for review in this repo, either in the current directory or in a new isolated worktree at ../yaak-worktrees/pr-. Use when asked to run or replace the old Claude check-out-pr command. ---- - -# Check Out PR - -Check out a PR by number and let the user choose between current-directory checkout and isolated worktree checkout. - -## Workflow - -1. Confirm `gh` CLI is available. -2. If no PR number is provided, list open PRs (`gh pr list`) and ask the user to choose one. -3. Read PR metadata: - - `gh pr view --json number,headRefName` -4. Ask the user to choose: - - Option A: check out in the current directory - - Option B: create a new worktree at `../yaak-worktrees/pr-` - -## Option A: Current Directory - -1. Run: - - `gh pr checkout ` -2. Report the checked-out branch. - -## Option B: New Worktree - -1. Use path: - - `../yaak-worktrees/pr-` -2. Create the worktree with a timeout of at least 5 minutes because checkout hooks run bootstrap. -3. In the new worktree, run: - - `gh pr checkout ` -4. Report: - - Worktree path - - Assigned ports from `.env.local` if present - - How to start work: - - `cd ../yaak-worktrees/pr-` - - `npm run app-dev` - - How to remove when done: - - `git worktree remove ../yaak-worktrees/pr-` - -## Error Handling - -- If PR does not exist, show a clear error. -- If worktree already exists, ask whether to reuse it or remove/recreate it. -- If `gh` is missing, instruct the user to install/authenticate it. diff --git a/crates/yaak-http/src/manager.rs b/crates/yaak-http/src/manager.rs index 19274b02..2034f124 100644 --- a/crates/yaak-http/src/manager.rs +++ b/crates/yaak-http/src/manager.rs @@ -1,7 +1,6 @@ use crate::client::HttpConnectionOptions; use crate::dns::LocalhostResolver; use crate::error::Result; -use log::info; use reqwest::Client; use std::collections::BTreeMap; use std::sync::Arc;