-
Notifications
You must be signed in to change notification settings - Fork 44
Update Bitbucket installation docs with IP allowlisting details #777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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 | |
|---|---|---|---|
| Infrastructure as Code | View in Orca | ||
| SAST | View in Orca | ||
| Secrets | View in Orca | ||
| Vulnerabilities | View in Orca |
|
Please mark which AI tools you used for this PR by checking the appropriate boxes:
Tip: If you want to avoid this comment in the future, you can add a label of the format |
There was a problem hiding this 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`. |
There was a problem hiding this comment.
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".
| - 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`. |
MishaKav
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💪
✨ PR Description
Purpose: Update Bitbucket installation documentation with comprehensive IP allowlisting instructions for various runner configurations.
Main changes:
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀