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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: sourcebot-dev/sourcebot-helm-chart
Length of output: 313
🏁 Script executed:
Repository: sourcebot-dev/sourcebot-helm-chart
Length of output: 1289
🏁 Script executed:
Repository: sourcebot-dev/sourcebot-helm-chart
Length of output: 366
Update actionlint before merging.
vulnerability-alerts: readis a supported GitHub Actions permission, but actionlint 1.7.12 rejects it as an unknown permission scope. Upgrade actionlint to a version that includes this scope, or configure the linter to tolerate it.🧰 Tools
🪛 actionlint (1.7.12)
[error] 12-12: unknown permission scope "vulnerability-alerts". all available permission scopes are "actions", "artifact-metadata", "attestations", "checks", "contents", "deployments", "discussions", "id-token", "issues", "models", "packages", "pages", "pull-requests", "repository-projects", "security-events", "statuses"
(permissions)
🤖 Prompt for AI Agents
Source: Linters/SAST tools