Conversation
A linked Server pull request never received host status, because every Bitbucket read went to api.bitbucket.org. Server clones are now recognized from their path, and list, get, and link sync read /rest/api/1.0 on the git remote's own origin with the existing Bitbucket token. 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
A linked Bitbucket Server pull request is read from the git remote's own origin at
/rest/api/1.0/projects/{key}/repos/{slug}/pull-requests/{id}. Server clones are recognized from/scm/{project}/{repo}.gitor SSH port 7999, including when the hostname containsbitbucket. List, get, and link sync use that API. Review reads return the same status with an empty diff and activity. Writes are refused so they are not sent to Bitbucket Cloud.The existing
T3CODE_BITBUCKET_ACCESS_TOKENis sent as Bearer. When it is unset,T3CODE_BITBUCKET_EMAILandT3CODE_BITBUCKET_API_TOKENare sent as Basic.bitbucket.orgstill usesapi.bitbucket.org.Why
Recognizing the URL only stored the link. Status never arrived, because every Bitbucket read went to
api.bitbucket.org.UI Changes
No new controls. A linked Server review can show the status this read returns. Screenshots and a video were not captured: this session has no Browser panel, which test-t3 requires.
Checklist
Grok 4.7, Cursor cloud agent.