Skip to content

ci(ai-review): add AI review workflow#5

Open
vklimontovich wants to merge 1 commit into
masterfrom
ci/add-ai-review
Open

ci(ai-review): add AI review workflow#5
vklimontovich wants to merge 1 commit into
masterfrom
ci/add-ai-review

Conversation

@vklimontovich
Copy link
Copy Markdown

Add the shared AI review workflow (pinned to 1.28.20260529), matching the documented policy for this repo. Runs on every PR and on direct pushes to master.

Copy link
Copy Markdown

@jitsu-code-review jitsu-code-review Bot left a comment

Choose a reason for hiding this comment

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

Reviewed .github/workflows/ai-review.yml for workflow correctness and security posture. I found two actionable issues:

  1. The reusable workflow is referenced by a mutable tag rather than an immutable commit SHA.
  2. The caller workflow does not declare token permissions, which can cap the called workflow and break review/comment posting in repos configured with read-only defaults.


jobs:
ai-review:
uses: jitsucom/github-workflows/.github/workflows/ai-review.yml@1.28.20260529
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This uses: pin is a mutable tag. If the upstream tag is moved, this repo will execute different workflow code without any change in this repository. For supply-chain safety and reproducibility, pin to an immutable commit SHA (optionally keep the tag in a comment for readability).

required: false

jobs:
ai-review:
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Could we add an explicit permissions: block in the caller workflow? In workflow_call, the called workflow permissions are capped by the caller token permissions. If this repo/org default is read-only, the called workflow can fail when it tries to publish commit comments/reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant