Changelog: Bitbucket Integration Setup - #72
Conversation
- Updated platform/repositories.mdx - Created Bitbucket-Grant-User-Repository-Access.png - Created Bitbucket-Create-Group.png - Created Grant-Group-Admin-Permission.png - Created Integration-Bitbucket.Png - Created Bitbucket-Integration-Authorisation.png - Created Bitbucket-Integration-RepoSelection.png - Created Bitbucket-Integration-Webhook.png - Moved changelog.mdx - Moved white-box-pentest/overview.mdx - Moved code-review/overview.mdx - Created platform/repositories/bitbucket.mdx - Updated docs.json Mintlify-Source: dashboard-editor
mintlify
Bot
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0d3a583095
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -0,0 +1,86 @@ | |||
| --- | |||
| title: "Bitbucket" | |||
| description: "Configure repository access for Bitbucket and self-hosted Bitbucket." | |||
There was a problem hiding this comment.
The page description advertises configuration for self-hosted Bitbucket, but the support section explicitly states that Bitbucket Data Center and other self-hosted deployments are not supported. This contradictory metadata can send self-hosted customers to instructions that cannot work; limit the description to Bitbucket Cloud.
Useful? React with 👍 / 👎.
| className="dark:hidden" | ||
| /> | ||
| <img | ||
| src="Bitbucket-Integration-Authorisation.png" |
There was a problem hiding this comment.
When a reader uses dark mode, this relative URL resolves beneath the current documentation route (for example, /platform/repositories/Bitbucket-Integration-Authorisation.png) rather than to the newly added root-level asset. As a result, the authorization screenshot is broken only in dark mode; use the same leading-slash path as the light-mode image.
Useful? React with 👍 / 👎.
Follow-up to the dashboard editor import in #72. - Move the seven Bitbucket screenshots out of the repo root into images/, renamed to the provider_thing.png convention used by the azure_* set. - Fix the dark-mode authorisation image, which had a relative src and so never loaded. Both variants pointed at the same file, so collapse them into a single img and drop the copy-pasted GitLab alt text. - Switch the remaining markdown images to the img form the other provider pages use. - Drop the self-hosted claim from the page description; the page itself says Data Center is not supported. - Add a Bitbucket card to the Code Review setup page alongside GitHub, GitHub Enterprise Server, GitLab, and Azure DevOps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 participant
Mintlify
0 threads from 0 users in Mintlify