Pavel Vaks

Hey @julijaciric, Thanks for reaching out, Your enthusiasm for gitstream is very much appreciated! This is indeed a valuable enhancement, which is on our radar, and planned for H1 2024....

Hi @IvanRibakov. Thanks for reaching out. We have increased the granularity of the triggering mechanism by adding support for including or excluding branches and repositories using strings or regexes. [Docs...

Hi @TRAD-Anthony-CKO, thanks for raising this issue We are planning to add a `cron` trigger. But I'd like to make sure that our planned feature will address this use case...

Hi @floskel, The problem reported in this issue is an issue with the `merge` action on repositories that use rulesets. Is this the same issue you are experiencing?

Can you please share the method `code-quality-assurance` updates its check? We have recently found that check resolutions via API calls fails to trigger the `merge` action. This is currently under...

Hi @matthewparavati and @codfish, Converting `require-reviewers` to a managed action is a roadmap item we plan to address in 2025. Currently, check status are updated only after commits. The plan...

Hi @gennadijbgl, I'm looking into this issue. Can you please share how you define the `author` variable?

/gs run `{{ source | LinearB_AI(prompt="Perform a detailed code review of the provided code diff. For each modified file: 1. Identify issues that require changes (e.g., bugs, performance, readability, or...

/gs run `{{ source | LinearB_AI(prompt="Perform a **precise code review** based on the provided diff. Identify **only necessary changes** (e.g., bugs, performance, readability, maintainability). **Ignore** descriptions of already implemented changes....

/gs run `{{ source | LinearB_AI(prompt=" Perform a **precise code review** based on the provided diff. Identify **only necessary changes** (e.g., bugs, performance, readability, maintainability) to the new code. **Don't**...