fix(guardrails): use project-scoped path for team worktree (Issue #155)#158
fix(guardrails): use project-scoped path for team worktree (Issue #155)#158
Conversation
The yard() function was creating directories in the parent directory (e.g. ~/Developer/.opencode-opencode-team) instead of within the project. Changed to use .opencode/team inside the project directory, matching the established project-scoped pattern. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
New PR opened -- automated review will run on the next push. To trigger a manual review, comment |
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: |
There was a problem hiding this comment.
Pull request overview
Updates the Guardrails team plugin to place delegated git worktrees in a project-scoped directory (<project>/.opencode/team) rather than creating hidden directories alongside the project’s parent folder, reducing filesystem clutter and keeping state local to the project.
Changes:
- Adjust
yard()to returnpath.join(dir, ".opencode", "team")for team worktree placement.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
yard()function inteam.tsthat was creating worktree directories in the parent directory (e.g.~/Developer/.opencode-opencode-team) instead of within the projectpath.join(dir, ".opencode", "team")to keep team data scoped inside the project's.opencode/directory, matching the established patternCloses #155
Test plan
yard()returns<project>/.opencode/teaminstead of<parent>/.<project>-opencode-teamyardadd()creates worktrees under.opencode/team/within the project🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com