resolveRepository returned an explicit repository before the unsupported-host guard, so getRepositoryCloneUrls with a self-hosted Bitbucket context still sent its read to the Cloud API. Run the guard first and cover that path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Victor Vogel committed on 10/24/2026, 2:29:02 AMparente1e024c
Checks
- SuccessfulCodeRabbitGitHub
Review completed
- Successful
Skipped - Not affected
- SuccessfulCheckGitHub
- SkippedRelease SmokeGitHub
- SkippedRustGitHub
- Skipped
- SuccessfulTestGitHub
- SuccessfulBuild and TypecheckGitHub
- SuccessfulTest WebGitHub
- SuccessfulLabel PR 22029GitHub
- Skipped
- SuccessfulLabel PR sizeGitHub
- SkippedDeploy relay previewGitHub
- SkippedEAS PreviewGitHub
- SkippedDeploy web previewGitHub
- SuccessfulLintGitHub
- SuccessfulTest Server 4GitHub
- SuccessfulNative fingerprint diffGitHub
- SuccessfulTest Server 8GitHub
- SuccessfulTest Server 1GitHub
- SuccessfulTest Server 5GitHub
- SuccessfulTest Server 6GitHub
- SuccessfulTest Server 3GitHub
- SuccessfulTest Server 7GitHub
- SuccessfulTest Server 2GitHub
- SuccessfulChangesGitHub
- SuccessfulCollect PR targetsGitHub
- SuccessfulPrepare PR size configGitHub
2 files changedLine totals unavailable