GitHub Actions artifact preflight

Catch hidden-file artifact gaps before a CI run ships the wrong bundle.

Paste a sanitized upload-artifact step. The checker reviews hidden file inclusion, path breadth, overwrite behavior, compression, and retention without reading repository files or uploading anything.

Static YAML checkNo repo accessSafe copy report

Artifact step

No file upload

Repository contextupload-artifact workflow step

Do not paste secrets, tokens, private build logs, or full workflow files. This page checks artifact input fields only.

fail

Artifact result

fail

The pasted artifact step has likely hidden-file or artifact upload blockers.

Findings1

Failures1

Warnings0

Hidden hints2

fail

Hidden paths are listed but include-hidden-files is not true

upload-artifact v4.4+ excludes hidden files by default. Explicit dotfile paths need include-hidden-files: true after you verify they contain no secrets.

Parsed fields

version: v4include-hidden-files: not setoverwrite: falsecompression: defaultretention: default

Safe report

GitHub Actions upload-artifact hidden files preflight
Status: fail
Summary: The pasted artifact step has likely hidden-file or artifact upload blockers.

Parsed step:
- action version: v4
- path: dist
.next/standalone
.coverage
- include-hidden-files: not set
- overwrite: false
- compression-level: default
- retention-days: default
- hidden path hints: .next/standalone, .coverage

Findings:
- fail: Hidden paths are listed but include-hidden-files is not true - upload-artifact v4.4+ excludes hidden files by default. Explicit dotfile paths need include-hidden-files: true after you verify they contain no secrets.

Checklist:
- Audit exact hidden paths before setting include-hidden-files: true.
- Avoid broad artifact paths when a smaller explicit output folder works.
- Decide whether overwrite should be true for same-name artifacts.
- Run the real workflow after this static preflight.

What this checks

It checks upload-artifact inputs for hidden-file exclusion, broad paths, overwrite behavior, compression-level, retention-days, and migration-sensitive defaults.

What this does not do

It does not inspect your repository, upload artifacts, verify GitHub storage policy, run a workflow, or prove that a bundle contains every file.