Skip to content

Conversation

@vim-zz
Copy link
Collaborator

@vim-zz vim-zz commented Aug 21, 2025

Screenshot 2025-08-21 at 12 53 48 Screenshot 2025-08-21 at 12 53 52

✨ PR Description

Purpose: Update Bitbucket installation documentation with comprehensive IP allowlisting instructions for various runner configurations.
Main changes:

  • Renamed info section heading to "Advanced: IP Allowlisting for gitStream" for better categorization
  • Added instruction to enable Atlassian IP ranges in bitbucket-pipeline.yml configuration
  • Restructured pipeline example with clearly commented sections for both cloud and self-hosted runners

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀

@vim-zz vim-zz requested a review from MishaKav August 21, 2025 09:54
Copy link

@orca-security-us orca-security-us bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed SAST high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

@gitstream-cm
Copy link
Contributor

gitstream-cm bot commented Aug 21, 2025

Please mark which AI tools you used for this PR by checking the appropriate boxes:

  • GitHub Copilot
  • Cursor
  • ChatGPT
  • Tabnine
  • JetBrains AI Assistant
  • VSCode IntelliCode
  • Claude
  • Gemini
  • Other AI tool
  • No AI tools were used

Tip: If you want to avoid this comment in the future, you can add a label of the format 🤖 ai-* when creating your PR.

Copy link
Contributor

@gitstream-cm gitstream-cm bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✨ PR Review

The PR updates Bitbucket installation documentation with IP allowlisting configuration details. The changes provide helpful guidance for both cloud and self-hosted runners, but there's a grammar error that needs correction.

1 issues detected:

🧾 Readability - The sentence contains duplicate words making it grammatically incorrect.

Details: There is a redundant word in the bullet point instruction that makes the sentence grammatically incorrect and confusing to readers.
File: docs/bitbucket-installation.md (39-39)

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀


- Add LinearB/gitStream service IPs to your Bitbucket allowlist (listed above).
- Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly.
- Add must add to your `bitbucket-pipeline.yml` `step.runtime.cloud.atlassian-ip-ranges: true`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧾 Readability - Grammar Error: Remove the redundant "Add" at the beginning of the sentence. Change "Add must add to your" to "Must add to your" or "Add to your".

Suggested change
- Add must add to your `bitbucket-pipeline.yml` `step.runtime.cloud.atlassian-ip-ranges: true`.
- Add to your `bitbucket-pipeline.yml` `step.runtime.cloud.atlassian-ip-ranges: true`.

Copy link
Collaborator

@MishaKav MishaKav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💪

@gitstream-cm gitstream-cm bot requested a review from a team August 21, 2025 09:56
@vim-zz vim-zz merged commit 7f630ed into main Aug 21, 2025
14 checks passed
@vim-zz vim-zz deleted the address-bb-whitelist branch August 21, 2025 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants