fix(status): report the repo's own origin host in status --json, not the auth target #459
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!459
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-429-status-host"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
madtea status --jsonset.hostto the configured/authenticated server host instead of the current repo's own origin remote host, so a clone whose origin points at a different forge than the auth target reported the wrong host (.owner/.repowere already correct). The cwd path in repoIdentity now resolves the origin host first (ADR 0025 origin-first chain) via a new statusOriginHost seam and the shared config.ParseRemoteHost, and only falls back to the configured host when the repo has no origin. The dir path (madt_status dir=) drops its hand-rolled URL parser and reuses the same shared parser, so both surfaces report the same host for the same origin, an explicit port included, and a latent port-drop on ssh://git@host:PORT is fixed. Credentials are stripped on every path. Adds regression tests: origin-host-wins-over-auth, no-origin fallback, credential strip, and port preservation on both paths.Closes #429