feat: add bitbucket developer docs#295
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughA new documentation page for the Bitbucket self-hosting integration is added, covering setup for both Bitbucket Cloud and Bitbucket Data Center. A matching sidebar navigation entry is registered in the VitePress config under the Integrations section. ChangesBitbucket Integration Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/self-hosting/govern/integrations/bitbucket.md`:
- Line 38: The document uses h4 headings (####) that skip the h3 level,
violating the heading-increment lint rule which requires headings to increment
by only one level at a time. Change all h4 headings (####) to h3 headings (###)
to maintain proper hierarchy between the surrounding h2 sections (##). This
includes the "Bitbucket Cloud" heading and the heading on line 75 mentioned in
the comment, and any other similar h4 headings in the document that jump
directly from h2 sections.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3a3562ba-ba88-4a88-b71e-219bc2d7e7c8
📒 Files selected for processing (2)
docs/.vitepress/config.mtsdocs/self-hosting/govern/integrations/bitbucket.md
|
|
||
| Follow these steps to register an OAuth consumer in your Bitbucket workspace, set the callback URL and scopes, and then configure your Plane instance so it can sync pull requests and commits. | ||
|
|
||
| #### Bitbucket Cloud |
There was a problem hiding this comment.
Use h3 headings here.
These #### headings jump too far from the surrounding ## sections and will fail the heading-increment lint rule. Drop them to ### (or remove the duplicate headings and rely on the tab labels).
Suggested fix
-#### Bitbucket Cloud
+### Bitbucket Cloud
@@
-#### Bitbucket Data Center
+### Bitbucket Data CenterAlso applies to: 75-75
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 38-38: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/self-hosting/govern/integrations/bitbucket.md` at line 38, The document
uses h4 headings (####) that skip the h3 level, violating the heading-increment
lint rule which requires headings to increment by only one level at a time.
Change all h4 headings (####) to h3 headings (###) to maintain proper hierarchy
between the surrounding h2 sections (##). This includes the "Bitbucket Cloud"
heading and the heading on line 75 mentioned in the comment, and any other
similar h4 headings in the document that jump directly from h2 sections.
Source: Linters/SAST tools
1 participant
Description
Type of Change
Summary by CodeRabbit