Skip to content

docs: Add change-pr-state automation action documentation#839

Merged
vim-zz merged 2 commits intomainfrom
doc/LINBEE-21553-change-pr-state-action
Jan 19, 2026
Merged

docs: Add change-pr-state automation action documentation#839
vim-zz merged 2 commits intomainfrom
doc/LINBEE-21553-change-pr-state-action

Conversation

@vim-zz
Copy link
Copy Markdown
Collaborator

@vim-zz vim-zz commented Jan 19, 2026

  • Add change-pr-state action to overview list
  • Document action parameters and usage
  • Include example for converting draft PRs to ready for review
  • Supports GitHub and GitLab platforms
image

✨ PR Description

Purpose: Add comprehensive documentation for the change-pr-state automation action, including usage patterns and platform support details.

Main changes:

  • Added change-pr-state action to table of contents with GitHub and GitLab platform badges
  • Documented change-pr-state action with parameter definitions, usage example, and explicit trigger requirements for draft PRs
  • Included note explaining that explicit triggers are required for draft PR automation due to gitStream's default execution model

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how

- Add change-pr-state action to overview list
- Document action parameters and usage
- Include example for converting draft PRs to ready for review
- Supports GitHub and GitLab platforms

Relates to LINBEE-21553
@vim-zz vim-zz requested a review from EladKohavi January 19, 2026 08:02
Copy link
Copy Markdown

@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 OSS Licenses 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

Copy link
Copy Markdown
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.

Lg

Copy link
Copy Markdown
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

LGTM

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how

@gitstream-cm gitstream-cm Bot requested a review from a team January 19, 2026 08:06
gitstream-cm[bot]
gitstream-cm Bot previously approved these changes Jan 19, 2026
@gitstream-cm gitstream-cm Bot dismissed their stale review January 19, 2026 08:09

Review dismissed

Copy link
Copy Markdown

@EladKohavi EladKohavi left a comment

Choose a reason for hiding this comment

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

It is ok but maybe we should specify that gitStream doesn't run on draft by default? or something like that

- Add informational note explaining gitStream doesn't run on draft PRs by default
- Link to execution model documentation for explicit triggers
- Update example comment for clarity

Since gitStream does not evaluate draft PRs by default, users must
configure explicit triggers (using the 'on' parameter) for automations
that use the change-pr-state action to function properly.
@gitstream-cm gitstream-cm Bot requested a review from a team January 19, 2026 11:51
@vim-zz vim-zz merged commit fcd0e33 into main Jan 19, 2026
13 checks passed
@vim-zz vim-zz deleted the doc/LINBEE-21553-change-pr-state-action branch January 19, 2026 12:00
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.

3 participants