Conversation
The link dialog rejected Server URLs such as
/projects/{key}/repos/{slug}/pull-requests/{id} when the host name did
not contain "bitbucket". That path is now trusted on any host, and the
stored repository is the checkout path scm/{project}/{repo} that an
HTTPS remote already records. SSH clones on port 7999 use the same key,
so pasting the browser URL matches the checked-out sub-repo. Server
links also generate Server browser URLs instead of Cloud ones.
Grok 4.7, Cursor cloud agent.
Co-authored-by: Gilad Leifman <Mizaro@users.noreply.github.com>
github-actions
Bot
added
vouch:trusted
Thread transfer impact
This comment will update automatically after the next completed run. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
The link dialog accepts a Bitbucket Server pull request URL,
/projects/{key}/repos/{slug}/pull-requests/{id}, on any host. The stored repository isscm/{project}/{repo}, the same path an HTTPS clone already records. An SSH clone on port 7999 uses that same key, so pasting the browser URL matches the checked-out sub-repo. Server links generate Server browser URLs.bitbucket.orgstays Bitbucket Cloud.Why
Pasting
https://git.example.com/projects/PROJ/repos/t3code/pull-requests/8623failed with "Use a pull request URL, 123, or pingdotgg#123." The parser only accepted Bitbucket Cloud paths, and only when the hostname containedbitbucket. A sub-repo checkout whose remote ishttps://host/scm/PROJ/repo.gitnever matched that URL.UI Changes
The link dialog now treats that Server URL as a pull request when the sub-repo is a project in the environment. Screenshots and a video were not captured: this session has no Browser panel (
preview_status/preview_open), which test-t3 requires, and the skill forbids switching to another automation system.Checklist
Grok 4.7, Cursor cloud agent.