Commit .squad?

[mcollier]

Should the .squad directory be committed? The docs mention committing .squad (or .ai-team). The squad-main-guard.yml workflow blocks a PR that contains the .squad folder.

[bradygaster]

I envisioned that squads would grow with repos. I understand some folks might want to put the .squad folder into their .gitignore. For awhile we had a guard up to prohibit folks from unintentionally pushing their .squad folder into their main branches; we did away with that. It got in the way of things. Nice to see you're using it @mcollier !

[bradygaster]

Great question, @mcollier! We've settled this design decision: .squad/ should be committed to your repo.

Squad is designed to grow with your repository. The .squad/ directory contains team charters, routing rules, and agent configurations that should be versioned and reviewed alongside code changes. We use a worktree-local strategy with merge=union driver for conflict-free merging.

We initially had a guard preventing .squad from being committed, but we removed it because it was overly restrictive. If you prefer to keep it local, you can add it to .gitignore, but the default pattern is to commit it.