fix: let directors start outside a git repo #1259

Merged

coilyco-ops merged 2 commits from issue-1112 into main

2026-07-14 09:39:35 +00:00

coilyco-ops commented

2026-07-14 09:33:49 +00:00

Member

Directors no longer fall back to the current directory's git origin when they resolve their default scope. The shared director scope path now depends on explicit --repo / --org flags or ~/.ward/config.yaml, which lets the director family start from any working directory without losing the backlog or merge surfaces.

removes the cwd git-origin fallback from the shared director scope resolver
updates the director, queue, and merge help text plus the director docs
adds regression tests for config-backed scope resolution and the no-git error path
closes #1112
ward.workflow: pull-request-and-merge
validation: targeted Go tests were blocked by the container's disk ceiling, so the branch was committed and pushed after source-level checks

Directors no longer fall back to the current directory's git origin when they resolve their default scope. The shared director scope path now depends on explicit `--repo` / `--org` flags or `~/.ward/config.yaml`, which lets the director family start from any working directory without losing the backlog or merge surfaces. - removes the cwd git-origin fallback from the shared director scope resolver - updates the director, queue, and merge help text plus the director docs - adds regression tests for config-backed scope resolution and the no-git error path - closes #1112 - ward.workflow: pull-request-and-merge - validation: targeted Go tests were blocked by the container's disk ceiling, so the branch was committed and pushed after source-level checks

coilyco-ops added 1 commit

2026-07-14 09:33:49 +00:00