Add documentation for subdomain matching in forge host determination

[Copilot]

Addresses feedback from #12564 requesting documentation of the subdomain matching logic in custom_host_matches_repository_host.

Changes

• Added doc comment explaining subdomain matching behavior with concrete examples
• Documents that api.example.com (account host) matches example.com (repo host)
• Clarifies the normalization + comparison logic

/// Checks if an account's custom host matches a repository host.
///
/// This function supports subdomain matching, where an account's custom host that is a
/// subdomain of the repository host will match. For example:
/// - Account host: `api.example.com`, Repository host: `example.com` → matches
/// - Account host: `gitlab.mycompany.com`, Repository host: `mycompany.com` → matches
/// - Account host: `example.com`, Repository host: `example.com` → matches (exact match)
///
/// The logic first normalizes both hosts (removing schemes, paths, ports, etc.) and then
/// checks if they are identical or if the account host ends with the repository host
/// prefixed by a dot (indicating it's a subdomain).
fn custom_host_matches_repository_host(repository_host: &str, account_custom_host: &str) -> bool {

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
gitbutler-web	Skipped		Feb 24, 2026 0:03am