-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitbucket provider does not return isDefault #7325
Comments
Thanks for reporting this, @jmls! This is probably related to #7366 as the default branch is also not detected in the Branches page. Cc @AlexTugarev @jldec because #7251 |
/assign @trumbitta |
@gtsiolis: GitHub didn't allow me to assign the following users: trumbitta. Note that only gitpod-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/schedule |
Bug description
when trying to run a prebuild in the dashboard , a bitbucket repo returns the error
"Error: Could not find a default branch in repository"
Steps to reproduce
press the "run preview" button and you get this error
Workspace affected
any bitbucket repo
Expected behavior
it should behave the same way as gitlab and github - ie run a prebuild
Example repository
No response
Anything else?
It looks like the Bitbucket API on a repo / branch does not return the information needed to check if the branch is the default.
the gitlab code is
return { host, owner, name, cloneUrl, description, avatarUrl, webUrl, defaultBranch };
the bitbucket code is
return { host, owner, name, cloneUrl, description, avatarUrl, webUrl };
There is an api call in BitBucket to obtain the default branch , but this is not implemented in the BitBucket provider code from gitpod.
The text was updated successfully, but these errors were encountered: