You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6aaa007
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(source-control): forges handle their own listing and SSH host quirks
Two flags still made the shared pull request service compensate for one forge,
and the order that decides which forge owns a URL or remote was written twice.
GitHub search can answer for a renamed repository with silence.
`listsAcrossMayOmitRepositories` had the service track which repositories
search had shown, for how long, and on which slice. The GitHub adapter now
keeps that cache and returns the repositories it cannot vouch for as
`unresolved`; the service reads those on their own without knowing why.
A Forgejo SSH remote names an alias, not the web server.
`sshRemoteHidesWebHost` had the service rewrite a recognised Forgejo provider
to "unknown" to force discovery, then take the web host from the result.
Source control providers now have an optional `resolveRemoteWebHost`;
Forgejo answers it from the login that serves the remote, and the service uses
whatever host it returns.
The definitions and their precedence now live in a small
`@t3tools/source-control-definitions` package that the server and clients
both import, and a server test checks its driver list matches them.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments