chore: add conductor.json for workspace setup#249
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| @@ -0,0 +1,6 @@ | |||
| { | |||
| "scripts": { | |||
| "setup": "ln -sf ~/repos/bazzalabs/ui/apps/web/.env.local apps/web/.env.local && bun install", | |||
There was a problem hiding this comment.
Hardcoded user-specific path breaks team portability
Medium Severity
The setup script uses a hardcoded absolute path ~/repos/bazzalabs/ui/apps/web/.env.local which assumes a specific directory structure on the developer's machine. This path will fail for any teammate whose repository is cloned to a different location (e.g., ~/code/, ~/projects/, or any other directory). Since conductor.json is committed to the repository and intended for team-wide workspace setup, this makes the configuration non-portable and will cause the symlink command to fail for most users.
Merge activity
|
Configures Conductor to automatically symlink .env.local and install dependencies when creating new workspaces.
137ccd2 to
609228b
Compare



Configures Conductor to automatically symlink .env.local and install
dependencies when creating new workspaces.