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 0e4df51
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(source-control): forges recognise their own remotes and repository keys
Shared and contracts held every forge's remote host rules, Azure DevOps's
repository key spellings (twice, plus a byte-for-byte copy in the server), the
Azure repository selector, and Forgejo's port-carrying change request host,
and the pull request service special-cased Forgejo SSH remotes, dev.azure.com
keys and a hardcoded list of public hosts.
Each forge's client definition now owns these behind hooks: recognizeRemote,
changeRequestHost, repositorySelector, repositoryKeyFromRemote,
canonicalRepositoryKey and sshRemoteHidesWebHost. The registry asks them in an
explicit recognition order that reproduces the old precedence, and falls back
to an unknown host. normalizeGitRemoteUrl is forge-neutral; persisted keys
come from the registry's repositoryKeyFromRemote, which keeps the old output
byte for byte (checked against a snapshot of every old function on ~90
remotes and keys). pullRequestHostOf, detectSourceControlProviderFromRemoteUrl,
canonicalRepositoryKey, sourceControlRepositorySelector and the GitHub-only
remote parser are gone. RepositoryIdentity.provider is now a
SourceControlProviderKind; the encoded value is unchanged.
Behaviour changes: agent session import names a project's repository for
every forge, not only GitHub. Forgejo's definition names codeberg.org as its
public host. The GitHub, GitLab and Bitbucket plugins consult only their own
recogniser, so a hostname carrying two forges' labels can now read as theirs
inside that plugin.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments