Update ticket description format and simplify PR description handling in bump-gitstream-core workflow [skip ci]

[MishaKav]

✨ PR Description

Purpose: Update the gitstream-core bump workflow to simplify commit messages and PR descriptions.

Main changes:

• Modified ticket description format from LINBEE-XXXX to LINBEE-XXXXX
• Removed version number from PR description, using only user-provided description
• Simplified commit message by removing redundant description

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

[orca-security-us]

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

[gitstream-cm]

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.

[jit-ci]

❌ Jit has detected 1 important finding in this PR that you should review.
The finding is detailed below as a comment.
It’s highly recommended that you fix this security issue before merge.

Repository Risks:

• Database Integration: Connects to a database, often involving sensitive data that must be securely managed.

Repository Context:

graph LR
    GitHub$Repository_U23_linear_U2D_b/gitstream_U2D_github_U2D_action["GitHub Repository<br/>linear-b/gitstream-github-action"]:::GitHub$Repository
    Team_U23_app_U2D_sec["Team<br/>app-sec"]:::Team
    Team_U23_Developers["Team<br/>Developers"]:::Team
    DBIntegration_U23_oracle["DBIntegration<br/>oracle"]:::DBIntegration
    Team_U23_app_U2D_sec -- "Owns" --> GitHub$Repository_U23_linear_U2D_b/gitstream_U2D_github_U2D_action
    Team_U23_Developers -- "Owns" --> GitHub$Repository_U23_linear_U2D_b/gitstream_U2D_github_U2D_action
    GitHub$Repository_U23_linear_U2D_b/gitstream_U2D_github_U2D_action -- "Is accessible to" --> DBIntegration_U23_oracle

Loading

[jit-ci]

Security control: Static Code Analysis Yaml

Shell Injection In Github Actions

Using variable interpolation ${{...}} with github context data in a run: step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. github context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with env: to store the data and use the environment variable in the run: script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR".

Severity: HIGH

Learn more about this issue

---

Jit Bot commands and options (e.g., ignore issue)

You can trigger Jit actions by commenting on this PR review:

• #jit_ignore_fp Ignore and mark this specific single instance of finding as “False Positive”
• #jit_ignore_accept Ignore and mark this specific single instance of finding as “Accept Risk”
• #jit_ignore_type_in_file Ignore any finding of type "Shell Injection in GitHub Actions" in .github/workflows/bump-gitstream-core.yml; future occurrences will also be ignored.
• #jit_undo_ignore Undo ignore command

[MishaKav]

#jit_ignore_accept