git

Prevent pushes to the default branch by enforcing topic-branch workflows. Create isolated branches with hyphenated names for each task, ensuring all work goes through proper review before merging to main, protecting the stability of your primary codebase.

Use Git worktrees to isolate multiple features or bug fixes in separate directories under .worktrees, each with its own branch. This keeps your main repository clean and lets you switch between tasks without stashing or committing incomplete work.

Create a worktree with `git worktree add .worktrees/branch-name -b branch-name`, list active worktrees with `git worktree list`, and remove finished worktrees with `git worktree remove .worktrees/branch-name` after merging changes back to main.

Topic branches with hyphenated names clarify task boundaries and improve collaboration. Clear naming conventions make it easier for teams to track which branch addresses which issue, simplify code reviews, and reduce merge conflicts in shared repositories.

Yes. Worktrees work seamlessly with standardized naming requirements. Combine worktree isolation with hyphenated topic-branch names to enforce team conventions while letting developers work on multiple tasks in parallel without workflow friction.

The workflow blocks direct pushes to the default branch, forcing you to create a topic branch instead. This safeguard ensures all changes undergo review and prevents unstable code from reaching production or breaking the main codebase.