Closed
Description
Can we add to our https://docs.coderabbit.ai/platforms/bitbucket-cloud either as a note or something, maybe just before App password creation,
If the Organization (workspace) has MFA enabled, then the CodeRabbit Bot User will also need to have MFA setup and enabled. Then they should create the app password and provide it to us.
We had a customer who had this setup, but didn't have MFA enabled for the CodeRabbit Service account they created. After a bunch of debugging, it started working
Metadata
Metadata
Assignees
Labels
No labels
Activity
linear commentedon May 16, 2025
ENG-1392 Bitbucket Docs Update [Request]
traycerai commentedon May 16, 2025
Plan
Observations
The Bitbucket Cloud docs (
docs/platforms/bitbucket-cloud.md
) cover app password generation but lack any mention of multi-factor authentication (MFA). This file consistently uses Docusaurus triple-colon admonitions (:::note
) for highlighting important info. The “Generating an App password” section is the natural insertion point for an MFA reminder. Official Atlassian documentation for two-step verification is available at https://support.atlassian.com/bitbucket-cloud/docs/enable-two-step-verification/.Approach
Modify the Markdown file to insert a concise admonition using the existing
:::note
syntax immediately above the “Generating an App password” heading. The note will inform readers that MFA must also be enabled on the CodeRabbit Bot service account if the workspace enforces MFA, and link to the Atlassian guide. After editing, preview locally with the Docusaurus dev server to ensure consistent rendering, then commit and open a PR.Reasoning
I analyzed the file structure and style of the Bitbucket Cloud docs, confirmed absence of any MFA guidance, researched Atlassian MFA links, and drafted precise copy aligning with existing note conventions.
Proposed File Changes
📄 docs/platforms/bitbucket-cloud.md (MODIFY) 🔗
Import In IDE
Developer Humor
Execution Information
Branch: main
Commit: a3f2a46
💡 Tips
Supported Commands (Inside Comments)
@traycerai generate
to iterate on the previous version of the implementation plan.Supported Commands (Inside Description)
@traycerai ignore
anywhere in the ticket description to prevent this ticket from being processed.@traycerai branch:<branch-name>
anywhere in the ticket description to specify the target branch for the implementation plan.Community
jmacdotorg commentedon Jun 2, 2025
@karan925 I think a simple step would suffice here; have a look.