close-session

To safely tear down a git worktree session, you must merge changes into main, stop the dev server, and remove the worktree and branch. This process prevents data loss and avoids repository drift.

Deleting an unmerged git worktree risks losing uncommitted work. Safe teardown processes include safeguards that detect unmerged changes and prevent accidental deletion of your active branch.

Closing a worktree session cleanly stops the dev server and cleans up occupied ports during a controlled teardown. This reclaims system resources and ensures no lingering background processes remain.

Yes, a mandatory session file documenting the teardown details must be created before removing a git worktree. This log verifies prerequisites and records the merge state before final cleanup.

No, worktree teardown safeguards prevent running the process from inside the main repository. The workflow targets short-lived worktree branches specifically and blocks execution in the main workspace to protect core files.

The best way to manage multiple short-lived git worktrees is using a single-step teardown workflow that merges into main, stops the dev server, and removes the worktree and branch. This streamlines workflows and reclaims resources.