You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After configuring bitbucket for and the correct workspace, when setting up a new application I expect the repository branches to load correctly, currently the api call to bitbucket.getBitbucketBranches throws a 400/404
Provide environment information
Operating System:
OS: Ubuntu 24.10
Arch: arm64
Dokploy version: v0.16.1
VPS Provider: DigitalOcean
What applications/services are you trying to deploy?
Next.js App
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
The text was updated successfully, but these errors were encountered:
Looks like the issue stems from how the repo "slug" is being handled in the API call. The API call is using the repository name instead of slug, i.e. Project Repo when it should use project-repo
Yes, I think it's more of a documentation error, for workspaces you should use the slug of your organisation/space, I will transfer this issue to the docs!
To Reproduce
Current vs. Expected behavior
After configuring bitbucket for and the correct workspace, when setting up a new application I expect the repository branches to load correctly, currently the api call to bitbucket.getBitbucketBranches throws a 400/404
Provide environment information
Operating System: OS: Ubuntu 24.10 Arch: arm64 Dokploy version: v0.16.1 VPS Provider: DigitalOcean What applications/services are you trying to deploy? Next.js App
Which area(s) are affected? (Select all that apply)
Application
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
The text was updated successfully, but these errors were encountered: