Add ward git remote (get-url) read passthrough #119

New issue

Closed

opened 2026-06-17 21:24:24 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-17 21:24:24 +00:00

Owner

Why

goose-triage resolves the default target repo from the current git origin (git remote get-url origin, parsed to an owner/name slug). ward git covers status/log/diff/add/fetch/pull/push/branch/checkout/stash/restore but has no remote verb ("No help topic for 'remote'"), so this is the one bare-git call left in the setup.

Asked-for surface

ward git remote get-url <name> (and ideally plain ward git remote to list) - a read passthrough, same shape as ward git status.

Context: agentic-os goose-triage swap-to-ward (agentic-os#237).

## Why goose-triage resolves the default target repo from the current git origin (`git remote get-url origin`, parsed to an owner/name slug). `ward git` covers status/log/diff/add/fetch/pull/push/branch/checkout/stash/restore but has no `remote` verb ("No help topic for 'remote'"), so this is the one bare-git call left in the setup. ## Asked-for surface `ward git remote get-url <name>` (and ideally plain `ward git remote` to list) - a read passthrough, same shape as `ward git status`. Context: agentic-os goose-triage swap-to-ward (agentic-os#237).

coilysiren referenced this issue from coilyco-flight-deck/agentic-os

2026-06-17 21:27:48 +00:00

Swap goose-triage fully onto ward (drop bare goose / coily / git) #239

coilysiren referenced this issue from a commit

2026-06-18 01:30:32 +00:00

feat(git): add remote read passthrough (ward#119)

coilysiren closed this issue

2026-06-18 01:30:32 +00:00

coilysiren referenced this issue from a commit

2026-06-18 01:30:32 +00:00

Merge issue-119: ward git remote read passthrough (closes #119)