project get/set-vikunja cwd fallback fails from a repo subdirectory #10

New issue

Closed

opened 2026-08-14 16:33:58 +00:00 by gravityfargo · 0 comments

gravityfargo commented

2026-08-14 16:33:58 +00:00

Owner

project get and project set-vikunja default the name to the literal cwd basename (Path.cwd().name). Invoked from a subdirectory of a registered project, the basename doesn't match the registry and resolution fails with no project named '…'.

Consider resolving the git top-level's basename instead (falling back to the cwd outside a repo), or explicitly documenting the run-from-root constraint in the verbs' help text. The consuming skills (todo, wrap-up) assume the cwd default works anywhere inside the project.

`project get` and `project set-vikunja` default the name to the literal cwd basename (`Path.cwd().name`). Invoked from a subdirectory of a registered project, the basename doesn't match the registry and resolution fails with `no project named '…'`. Consider resolving the git top-level's basename instead (falling back to the cwd outside a repo), or explicitly documenting the run-from-root constraint in the verbs' help text. The consuming skills (todo, wrap-up) assume the cwd default works anywhere inside the project.

gravityfargo referenced this issue from a pull request that will close it,

2026-08-14 16:42:22 +00:00

feat(project): projects registry with git origin detection and vikunja mapping #11

gravityfargo closed this issue

2026-08-14 16:45:23 +00:00