ci: split dependency capture from review comments - #30
Draft
kiranmagic7 wants to merge 3 commits into
Draft
Conversation
Signed-off-by: Kiran <262980978+kiranmagic7@users.noreply.github.com>
Signed-off-by: Kiran <262980978+kiranmagic7@users.noreply.github.com>
Signed-off-by: Kiran <262980978+kiranmagic7@users.noreply.github.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.
Implements issue #21 on top of the hosted-green canary/import/sinkhole branch.
This adds a data-only dependency-review artifact contract, strict artifact and GitHub-run validation, and separate unprivileged capture and privileged comment workflows. The pull-request job checks out only the trusted base revision, reads exact manifests through the GitHub API, receives no secrets or write permissions, and never executes pull-request repository code. The workflow_run job checks out only the default branch, independently verifies the triggering run and bounded artifact, regenerates escaped Markdown, and holds only the permissions required to update one bot-owned comment.
Safety boundary: there is no pull_request_target workflow, no pull-request-head checkout, no self-hosted runner, no identity token, and no execution of artifact content. The privileged workflow remains inactive until reviewed and merged to the default branch; this draft PR does not launch or publish anything.
Verification before push: make check and scoped gosec passed after rebasing onto agent/canary-import-sinkhole-observations.
Tracks #21.