[codex] Add checked-in GitHub Actions consumer workflow example#38
[codex] Add checked-in GitHub Actions consumer workflow example#38
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 754b2cd4ec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - name: Upload dependency diff outputs | ||
| uses: actions/upload-artifact@v7 |
There was a problem hiding this comment.
Upload artifacts even when threshold check fails
If new_package_count exceeds the threshold, the prior step exits non-zero, and this upload step is skipped because GitHub Actions applies a default success() condition to steps without an explicit status check. In that common policy-failure scenario, the workflow drops report.json, report.md, summary.json, and report.sarif, which prevents reviewers from inspecting the exact failure output; add an explicit condition such as if: ${{ always() }} (or !cancelled()) on the upload step to retain artifacts for failed runs.
Useful? React with 👍 / 👎.
Brief Design Summary
This PR adds a checked-in GitHub Actions consumer workflow example for
sbom-diff-risk.The example lives under
tools/sbom-diff-and-risk/examples/, not.github/workflows/, so it is documentation/example material for consumer repositories to copy if useful. It installs from thev0.6.0GitHub Release wheel, runscompare, writes JSON, Markdown, summary JSON, and SARIF outputs, applies an explicit localsummary.jsonthreshold, and uploads the generated files as CI artifacts.Production PyPI remains intentionally deferred. The example does not use secrets, real internal paths, private repository names, production PyPI, hidden network behavior, or built-in dependency safety verdict claims.
Files Changed
tools/sbom-diff-and-risk/examples/github-actions-consumer.ymltools/sbom-diff-and-risk/docs/github-actions-consumer-example.mdtools/sbom-diff-and-risk/README.mdValidation
git diff --checkpassed.Cf/Ccscan on touched files; no non-tab/newline control or format characters found..github/workflows/unchanged.0.6.0.Out of Scope