fix: refresh repository identity after SSH translation

[benekuehn]

Summary

• refresh cached remote metadata after resolving SSH host aliases
• preserve fetch URL precedence, falling back to push metadata when the fetch URL cannot be parsed

Root cause

repository.Current translated the fetch and push URLs, but the cached Host, Owner, and Repo fields still described the pre-translation URL. Known-host filtering therefore rejected remotes that used SSH aliases for GitHub.

Testing

• go test ./...
• go vet ./...

Related issues

• Relates to gh stack submit fails when remote uses a custom SSH host alias github/gh-stack#45
• Relates to Remapping hostname prevents using gh stack submit github/gh-stack#337

[RishabJaiswal]

Request to merge this urgently

Quite a common usecase for users with multiple github accounts

[Copilot]

Pull request overview

This PR fixes incorrect remote host/owner/repo identity caching when SSH hostname aliases are translated, ensuring host-based filtering works against the post-translation canonical hostname (e.g., github.com).

Changes:

• Refactors SSH URL translation into translateRemotes and refreshes Remote{Host,Owner,Repo} after translation.
• Preserves fetch URL metadata precedence, falling back to push URL metadata only when fetch repo info cannot be derived.
• Adds unit tests covering SSH alias translation and the fetch-to-push fallback behavior.

Show a summary per file

File	Description
pkg/repository/repository.go	Translates remotes via a helper and refreshes cached remote identity fields after SSH alias resolution, with fetch-first fallback semantics.
pkg/repository/repository_test.go	Adds tests validating remote identity refresh after translation and fallback to push URL when fetch repo info is invalid.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite