update docs with bitbucket triggers warning #719
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![orca-security-us[bot]](https://avatars.githubusercontent.com/in/276250?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
Contributor
|
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 |
![gitstream-cm[bot]](https://avatars.githubusercontent.com/in/230441?s=60&v=4){kind=small}
docs/bitbucket-installation.md
Outdated
| The `add-label` action is not supported in Bitbucket as Bitbucket does not have a native labeling feature. | ||
|
|
||
| !!! warning "Explicit triggers are not supported" | ||
| The `triggers` and `on` functionality are not currently supported in Bitbucket. If you include them in your CM automation files, gitStream will ignore them and will use the default triggering as sepecified in [`Trigger Control`](./execution-model.md#triggers-section). |
Contributor
There was a problem hiding this comment.
Suggested change
| The `triggers` and `on` functionality are not currently supported in Bitbucket. If you include them in your CM automation files, gitStream will ignore them and will use the default triggering as sepecified in [`Trigger Control`](./execution-model.md#triggers-section). | |
| The `triggers` and `on` functionality are not currently supported in Bitbucket. If you include them in your CM automation files, gitStream will ignore them and will use the default triggering as specified in [`Trigger Control`](./execution-model.md#triggers-section). |
Contributor
|
A screenshot of the relevant part of docs after the changes is a life saver 🛟 |
yeelali14
approved these changes
May 20, 2025
Contributor
✨ PR ReviewLGTM Generated by LinearB AI and added by gitStream. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✨ PR Description
Purpose and impact:
This PR updates documentation for Bitbucket and GitLab installations, clarifying limitations and adding warnings about unsupported features.
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! 🚀