Use local upload-sarif Action in PR checks job#3953
Open
henrymercer wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the PR checks workflow to use the repository’s local upload-sarif Action rather than referencing github/codeql-action/upload-sarif@v4, aligning with repository rules that require pinned Actions and avoiding an unpinned major tag reference.
Changes:
- Switch the
Upload sarifstep in the PR checks workflow touses: ./upload-sarif.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/pr-checks.yml |
Uses the local upload-sarif Action for uploading ESLint SARIF results instead of @v4. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
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.
Use the local
upload-sarifAction in PR checks job instead of referencingv4. This reference otherwise interferes with repository rules about pinned Actions.Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
pr-checks).If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
CI
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist