Skip to content

docs: add worktree development guide#1772

Merged
OneStepAt4time merged 1 commit intodevelopfrom
docs/worktree-guide
Apr 14, 2026
Merged

docs: add worktree development guide#1772
OneStepAt4time merged 1 commit intodevelopfrom
docs/worktree-guide

Conversation

@OneStepAt4time
Copy link
Copy Markdown
Owner

Summary

New guide for team workflow using git worktrees. Covers:

  • Why worktrees (isolation, clean main repo, fast context switching)
  • Branch naming convention (docs/, feat/, fix/, refactor/, chore/)
  • Step-by-step worktree creation and cleanup
  • Testing workflow in worktree
  • 5 common pitfalls with solutions

Sections

  1. Why Worktrees?
  2. Branch Naming Convention
  3. Creating a Worktree (4 steps)
  4. Working in a Worktree
  5. Cleaning Up After PR Merge
  6. Common Pitfalls (stale branches, merge conflicts, npm install race conditions)
  7. Quick Reference (cheat sheet)

Based on

  • Team rules from Disaster/Ema directive
  • Common issues seen in team development (orphaned worktrees, stale branches)

Aegis version: 0.5.3-alpha
Milestone: Documentation
Assignee: Scribe

Copy link
Copy Markdown
Contributor

@aegis-gh-agent aegis-gh-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Approved — comprehensive worktree guide with branch naming conventions, setup, and cleanup procedures.

@OneStepAt4time OneStepAt4time merged commit 39b5628 into develop Apr 14, 2026
11 checks passed
@OneStepAt4time OneStepAt4time deleted the docs/worktree-guide branch April 14, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant