Share Drift Results with Your Team

Drift insight only helps when the team can see it. Vibgrate gives you three complementary ways to share: push the live DriftScore to Vibgrate Cloud, commit the code map so everyone's AI Context stays in sync, and generate a report file to attach to a PR. This tutorial uses all three.

Prerequisites

• The Vibgrate CLI installed (npm i -g @vibgrate/cli)
• A Vibgrate Cloud workspace
• A git repository

Steps

1. Push results to the dashboard

vg scan --push

Everyone with workspace access can now see the DriftScore in Vibgrate Cloud at dash.vibgrate.com.

2. Make the code map committable

vg share

This makes the code map committable and auto-updating for your team. It installs a pre-commit hook, a deterministic merge driver, and the right .gitignore entries, so the map stays fresh as people commit.

3. Generate a shareable report

vg report --format markdown --out drift-report.md

Markdown renders cleanly in PRs, wikis, and chat.

4. Attach the report to a PR

Commit drift-report.md or paste its contents into the PR description so reviewers see the drift impact alongside the code change.

5. Verify team access

Ask a teammate to open the dashboard and pull the latest commit. They should see the shared DriftScore and an auto-updating code map.

Verification

The dashboard shows the pushed scan, vg share exits 0 and adds the hook and merge driver, and the report file is present in the repo. Teammates see consistent drift data across all three channels.

Next Steps

• Keep the shared trend current automatically: "Schedule Recurring Drift Reporting".
• Give the whole org a single view: "Set Up a Portfolio View Across Repositories".