Repository navigation
ci: add trusted API identity checks alongside legacy checks - #67
Merged
Merged
Conversation
Signed-off-by: Vijay <evijay@gmail.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
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.
Summary
705d386a0917bc323b0f2ea1110f4e6e6bffa124, including the immutable-comparison pagination fix from collector #108.The
pull_request_targetworkflows have read-only permissions and never check out or execute PR code. Regression tests that execute PR code run separately onpull_requestwith persisted credentials disabled.Validation
Staged Rollout
This addition merges through the existing DCO and signature checks. The trusted checks must next pass on a real PR before their names replace the required legacy names. Cleanup merges only after the new required checks are active. No protection bypass, release or runtime change.