ci: include CodeQL in failure feedback - #423
Merged
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
CodeQL now joins the existing CI subscription. The reporter retains its reviewed local reusable workflow and places Actions read / Issues write only on the publisher job.
The completed-run trigger invokes reviewed publisher code, with no source-run code or artifact execution. Only exact run and attempt IDs enter typed inputs. Unsuccessful conclusions stay truthful; issues remain unassigned. The narrow dangerous-triggers annotation documents this metadata-only trust boundary. Runtime delivery for a new repository remains unproven until a natural failure occurs.
Permissions: the new/revised feedback job receives Actions read for metadata and Issues write for bounded repo-local evidence; workflow-level permissions are empty. There is no content, deployment, or agent-launch permission.
Validation: 20 publisher tests; full make verify on Go 1.26.7; actionlint.
Closes #422.