Skip to content

chore: add conductor.json for workspace setup #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kianbazza merged 1 commit into from
Mar 28, 2026
Merged

chore: add conductor.json for workspace setup #249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions conductor.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"scripts": {
"setup": "ln -sf ~/repos/bazzalabs/ui/apps/web/.env.local apps/web/.env.local && bun install",
Copy link
Copy Markdown

@cursor cursor Bot Feb 4, 2026

Choose a reason for hiding this comment

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

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.

Fix in Cursor Fix in Web

"run": "bun run dev --filter web"
}
}
Loading