Benson LUOandNeil 38fe0766c3 fix(gitlab): never resolve github.com or bitbucket.org remotes as GitLab projects (#40410) ...

A stray github.com or bitbucket.org entry in glab's config made the failed
`glab auth status --hostname <host>` probe print a status block headed by a
bare hostname, which the configured-host parser accepted as evidence. The
known-host inventory could likewise list github.com. Because GitLab has
precedence among forge providers, GitHub and Bitbucket repos were offered
GitLab merge requests and GitLab login prompts.

Before trusting any glab evidence, resolveProjectRefForRemote now returns null
when the remote's real host (aliases folded via normalizeForgeWebHost) is
github.com or bitbucket.org. Scp remotes on an SSH alias named e.g. `github`
are unaffected.

Fixes #40386

Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>

2026-11-09 18:48:58 -08:00

..

cli

test: remove low-value markdown, agent, and pricing cases (#40566)

2026-11-09 17:20:55 -08:00

main

fix(gitlab): never resolve github.com or bitbucket.org remotes as GitLab projects (#40410)

2026-11-09 18:48:58 -08:00

packages/process-host

test: remove 21 low-value tests and two suites (#40479)

2026-11-09 13:29:53 -08:00

preload

fix(i18n): translate sparse preset validation failures (#40277)

2026-11-09 15:12:50 -08:00

renderer

Keep chat navigation focused on human messages (#33403)

2026-11-10 02:34:03 +00:00

shared

Keep chat navigation focused on human messages (#33403)

2026-11-10 02:34:03 +00:00

types

…

wsl-guest

Fix false Codex worker readiness after startup (#40246)

2026-11-09 17:35:42 -08:00