Skip to content

ci(dataset-audit): upload findings always (AUREO-1483) #956

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeffreylouden merged 1 commit into from
Oct 17, 2026
Merged

ci(dataset-audit): upload findings always (AUREO-1483) #956

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .github/workflows/dataset-audit.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,11 @@ jobs:
# Every audit appends its settled findings to findings/findings.jsonl
# (see "Findings" in CLAUDE.md); the racks repo's file-findings.ts
# carries that file into the catalog-submissions inbox, one issue per
# finding, ever. The terminal reports are unchanged. Each audit is
# `|| true`: a red audit must not stop the next one or the issue
# update below, and the findings file is uploaded whatever happened.
# finding, ever. The terminal reports are unchanged. Each corpus
# audit is `|| true`, so a red one does not stop the next or the
# issue update. `dataset:audit` is not: the issue update parses its
# JSON, so its failure has to fail the job. The upload runs
# `always()`, so whatever was written still reaches the inbox.
- name: Generate dataset audit
id: audit
run: |
Expand All @@ -55,6 +57,7 @@ jobs:
wc -l findings/findings.jsonl || true

- name: Upload findings
if: always()
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
with:
name: audit-findings
Expand Down
Loading