Repository navigation
fix: escalate AI review risk from live PR labels #356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: electricsheephq/lcm-x
Length of output: 21237
🏁 Script executed:
Repository: electricsheephq/lcm-x
Length of output: 43494
🌐 Web query:
GitHub Actions concurrency cancel-in-progress running job cancellation semantics allowed contexts github.event pull_request number inputs expression💡 Result:
In GitHub Actions, the
concurrencykey is used to limit the number of simultaneous workflow runs or jobs within a defined concurrency group [1][2][3]. Concurrency Cancellation Semantics By default, GitHub Actions allows only one running instance and one pending instance within a single concurrency group at any time [1][4]. When a new job or workflow run is triggered: 1. If another run is already in progress in the same group, the new run is marked aspending[1][2]. 2. Any existingpendingrun in that group is automatically canceled to make room for the newpendingrun [1][4]. 3. Thecancel-in-progressoption, when set totrue, additionally cancels the currently running job or workflow in that group [1][5]. Expression Contexts Thecancel-in-progressproperty can accept a boolean value or an expression [1][4]. When using an expression, it must evaluate to a boolean and is restricted to the following allowed contexts: -githubcontext [3][6] -inputscontext [3][6] -varscontext [3][6] Whilegithub.event(such asgithub.event.pull_request.number) is accessible within expressions for thegroupkey, you should be aware that thegithubcontext contains different data depending on the event that triggered the workflow [6]. If your concurrency group or a conditionalcancel-in-progressexpression relies on properties that are only present in certain events (e.g.,github.event.pull_request.numberonly exists for pull request events), you must include a fallback to avoid errors during non-PR events [7]. A common pattern to handle this is: group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }} [8][9] This ensures that the concurrency group remains unique and valid regardless of the specific trigger event [7]. Additionally, ensure that concurrency group names are unique across different workflows in the same repository to avoid unintended cancellations of unrelated jobs [1][7].Citations:
🏁 Script executed:
Repository: electricsheephq/lcm-x
Length of output: 635
Coordinate all receipt writers per pull request.
A label reset can write
failure, then an older validation can writesuccessafter its final drift read. Addcancel-in-progress: trueand a regression assertion. Ensure the concurrency group also covers thepushreset path; agithub.run_idfallback leaves that writer uncoordinated. Confidence: 96%.actionlint .github/workflows/ai-review-gate.ymlexits 0.🤖 Prompt for AI Agents
Source: Linters/SAST tools