worktree-pr-and-clean

To automate git worktree cleanup after a PR, use a workflow that locates the active worktree, verifies a clean state, pushes the branch to origin, creates a PR via GitHub CLI, and then removes the worktree and prunes metadata.

Yes, you can create a GitHub pull request directly from a temporary git worktree if the GitHub CLI is installed and authenticated; otherwise, the workflow provides manual PR creation steps.

The safest way to push a feature branch from a git worktree is to first verify the worktree has a clean status and the expected branch is active, then push to origin and open a PR to main only after explicit user approval.

The worktree PR and cleanup workflow does not strictly require the GitHub CLI, but it uses the CLI to automatically open a PR to main; without it, the workflow outputs manual PR creation steps.

The worktree cleanup process handles stale git metadata by removing the temporary worktree, running git worktree prune to clear stale references, and clearing the active-worktree indicator file.

If a git worktree has uncommitted changes before PR creation, the workflow's state verification step fails because it requires a clean worktree status and the current branch to match the expected branch before pushing.