Skip to content

CID-19785 - Updload Sarif file directly to code scanning api#243

Draft
andrewlundberg-wf wants to merge 3 commits into
masterfrom
CID-19785
Draft

CID-19785 - Updload Sarif file directly to code scanning api#243
andrewlundberg-wf wants to merge 3 commits into
masterfrom
CID-19785

Conversation

@andrewlundberg-wf
Copy link
Copy Markdown
Contributor

Replaces the external github/codeql-action/upload-sarif composite step with an in-process SARIF upload using the GitHub REST API (code-scanning/uploadSarif). This gives the action direct control over the upload lifecycle, including retry logic and error handling.

This was done to support allowing the action to be used in public repositories.

@btr-rmconsole-6
Copy link
Copy Markdown

btr-rmconsole-6 Bot commented May 4, 2026

Merge Requirements Unmet ❌

Request Rosie to automerge this pull request by including @Workiva/release-management-p in a comment.

❌ All commits reviewed (1553c3c authored by andrewlundberg-wf)

General Information

Ticket(s):

Code Review(s): #243
Release Image Tags:

Reviewers: None

Additional Information

Watchlist Notifications: None

	When this pull is merged I will add it to the following release:
	Version: gha-security-scanner v0.1.2
	Release Ticket(s): None


Note: This is a shortened report. Click here to view Rosie's full evaluation.
Click here for documentation on the merge-requirements status check
Last updated on Tuesday, May 05 01:30 PM CST

@btr-github-actions
Copy link
Copy Markdown

btr-github-actions Bot commented May 4, 2026

Security Audit Results

Please direct questions to #support-infosec.

Commit Signing

✅ All commits are signed

Raven

✅ 40 global file checks pass
✅ 94 global keyword checks pass

Images

✅ No Dockerfiles in this PR

Workflows

.github/workflows/gha-security-scanner.yaml found.

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@andrewlundberg-wf andrewlundberg-wf marked this pull request as ready for review May 4, 2026 05:05
@andrewlundberg-wf andrewlundberg-wf requested review from a team as code owners May 4, 2026 05:05
Comment thread action.yml Outdated
Comment thread rollup.config.ts
const config = {
input: 'src/index.ts',
onwarn(warning, warn) {
if (warning.code === 'THIS_IS_UNDEFINED') return
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It removes unhelpful warnings that are being displayed in the build process

@andrewlundberg-wf andrewlundberg-wf marked this pull request as draft May 4, 2026 18:10
@zanehala-wk
Copy link
Copy Markdown
Contributor

zanehala-wk commented May 4, 2026

Do all we actually have to do here is just remove this

- name: 'Upload SARIF file as artifact'
uses: actions/upload-artifact@v7
with:
name: semgrep.sarif
path: semgrep.sarif

The main point of the ticket is removing the artifact from being publicly accessible. Is there a reason we upload it to the public artifact storage in the first place?

@cristianmartinello-wf
Copy link
Copy Markdown
Contributor

Do all we actually have to do here is just remove this

- name: 'Upload SARIF file as artifact'
uses: actions/upload-artifact@v7
with:
name: semgrep.sarif
path: semgrep.sarif

The main point of the ticket is removing the artifact from being publicly accessible. Is there a reason we upload it to the public artifact storage in the first place?

Not sure we can answer that question.

3ecd2fd

@andrewlundberg-wf
Copy link
Copy Markdown
Contributor Author

Do all we actually have to do here is just remove this

- name: 'Upload SARIF file as artifact'
uses: actions/upload-artifact@v7
with:
name: semgrep.sarif
path: semgrep.sarif

The main point of the ticket is removing the artifact from being publicly accessible. Is there a reason we upload it to the public artifact storage in the first place?

Not sure we can answer that question.

3ecd2fd

How about pushing this to a future ticket,

@andrewlundberg-wf andrewlundberg-wf marked this pull request as ready for review May 5, 2026 16:40
@zanehala-wk
Copy link
Copy Markdown
Contributor

zanehala-wk commented May 5, 2026

How about pushing this to a future ticket,

What I'm saying here is I think that the majority of this PR is unnecessary, the github/codeql-action/upload-sarif@v4 action already does do an upload of the SARIF file directly to the API, so there are likely no real code changes that need to occur here. We just simply needed to remove the actions/upload-artifact@v7 action.

@andrewlundberg-wf andrewlundberg-wf marked this pull request as draft May 5, 2026 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants