gooze report push

Packages the reports directory and pushes it to an OCI registry as an artifact. Use this to share baseline results with CI and teammates.

Usage

gooze report push <reference>

This packages the reports dir (-o/--output, default .gooze-reports) and pushes it as an OCI artifact.

Example

gooze report push ghcr.io/your-org/your-repo/gooze-reports:main

Flags

  • -o, --output <dir>: reports directory to package (default .gooze-reports)
  • --plain-http: use a non-TLS (HTTP) registry
  • --insecure: skip TLS certificate verification

Authentication

For registries that require login, set GOOZE_REGISTRY_USERNAME and GOOZE_REGISTRY_PASSWORD. The password may be a token/PAT — for GHCR, use your GitHub username with a PAT (or GITHUB_TOKEN in CI).

export GOOZE_REGISTRY_USERNAME="$USER"
export GOOZE_REGISTRY_PASSWORD="$GITHUB_TOKEN"
gooze report push ghcr.io/your-org/your-repo/gooze-reports:main

If unset, Gooze falls back to the Docker credential store (whatever docker login saved). See CI / GitHub Actions for a full workflow.