Opening a folder that isn't a Git repository adds it as a project (Cmd+O / Open folder…). After that, every New channel in that project fails with Could not start channel: <path> is not inside a Git repository, which comes from apps/host/src/manage.ts. Terms define a project as "one or more repositories or local folders", so the picker offers a project where channels can't be created.
Observed while validating #157:
- Setup: an isolated source host and a headless browser driving the real app.
fixtures/folder-only (a plain folder) opened as a project.- New channel failed with the error above. The error toast is visible in screenshot
05-picker and is recorded in the host's gateway.failed log entry.
- After
git init and a first commit, the same folder created channels normally.
Acceptance
Pick one and make the app consistent with it:
- start channels in a non-Git folder (no lanes, or lanes disabled with a clear reason), or
- explain at open time that the folder needs Git, before it appears as a project where channels can't be created.
Either way, update the terms and architecture docs if the meaning of "project" changes.
Dogfooding: #5.
Opening a folder that isn't a Git repository adds it as a project (Cmd+O / Open folder…). After that, every New channel in that project fails with
Could not start channel: <path> is not inside a Git repository, which comes fromapps/host/src/manage.ts. Terms define a project as "one or more repositories or local folders", so the picker offers a project where channels can't be created.Observed while validating #157:
fixtures/folder-only(a plain folder) opened as a project.05-pickerand is recorded in the host'sgateway.failedlog entry.git initand a first commit, the same folder created channels normally.Acceptance
Pick one and make the app consistent with it:
Either way, update the terms and architecture docs if the meaning of "project" changes.
Dogfooding: #5.