Push Drift Results to Vibgrate Cloud from CI

Vibgrate Cloud collects scan results across repositories so your team can track DriftScore trends in one dashboard. From CI, vg scan --push uploads each run, authenticated by a DSN token kept as a secret.

Prerequisites

• A Vibgrate Cloud workspace at dash.vibgrate.com.
• Vibgrate running in CI.

Steps

1. Create a DSN token

Generate an HMAC-signed DSN that the CLI uses to authenticate uploads.

vg dsn create

Copy the resulting token; treat it as a secret.

2. Store the DSN as a secret

Add the token to your CI secrets store, for example as VIBGRATE_DSN. Never commit it to the repository.

3. Push results with --push

Pass --push to upload the scan, providing the DSN from the secret.

vg scan --push --dsn "$VIBGRATE_DSN"

In the workflow, wire the secret into the environment.

      - run: npx @vibgrate/cli scan --push --dsn "$VIBGRATE_DSN"
        env:
          VIBGRATE_DSN: ${{ secrets.VIBGRATE_DSN }}

4. Tag the repository name

Give uploads a stable repository name so trends group correctly across runs.

vg scan --push --dsn "$VIBGRATE_DSN" --repository-name my-service

5. View trends in Vibgrate Cloud

Open dash.vibgrate.com and find your repository. Each pushed run adds a data point to the DriftScore trend.

Verification

After a CI run with --push, confirm a new scan appears in Vibgrate Cloud for the repository. If nothing shows up, check the DSN secret is set and that the push step ran without error (non-zero exit indicates an upload problem).

vg scan --push --dsn "$VIBGRATE_DSN"

Next Steps

• Push from a nightly scheduled scan for a steady trend line.
• Combine --push with a --drift-budget gate in the same run.
• Use vg report to also keep a local human-readable summary.