Files
vercel__next.js/conductor.json
T
Wyatt Johnson aa9c71671a fix: move conductor.json to repo root for proper detection (#88184)
## What?

Moves `conductor.json` from `.conductor/conductor.json` to the
repository root and updates script paths accordingly.

## Why?

Conductor searches for configuration files in a specific priority order:
1. Workspace root
2. Remote default branch
3. Repository root

The previous location at `.conductor/conductor.json` wasn't in the
standard search path, which could cause Conductor to not detect the
configuration properly. Moving to the repo root follows the [recommended
pattern from Conductor's
documentation](https://docs.conductor.build/core/conductor-json).

## How?

- Moved `conductor.json` to repository root
- Updated script paths from `./scripts/` to `./.conductor/scripts/`
- Scripts remain in `.conductor/scripts/` for organization
2026-01-06 17:55:45 -07:00

25 lines
685 B
JSON

{
"name": "next.js",
"description": "Next.js framework development workspace",
"scripts": {
"setup": "./.conductor/scripts/setup.sh",
"run": "./.conductor/scripts/run.sh"
},
"worktree": {
"default_branch": "canary"
},
"environment": {
"NEXT_TELEMETRY_DISABLED": "1",
"TURBO_TELEMETRY_DISABLED": "1"
},
"recommendations": {
"parallel_agents": 3,
"notes": [
"Each worktree uses ~500MB-1GB disk space after build",
"Run 'pnpm sweep' periodically to clean Rust build artifacts",
"Use 'pnpm test-dev-turbo' for fastest test iteration",
"Never run 'pnpm build' while 'pnpm dev' is active (causes corruption)"
]
}
}