When you push scan results, Vibgrate Cloud needs to know which repository they belong to so it can group them and chart trends correctly. This guide covers how to connect a repository by giving it a stable name on every upload.
Overview
A repository in Vibgrate Cloud is identified by name. Pushing results with a consistent repository name on each scan keeps all of that repo's history together. Using a different name each time fragments the history into separate, unrelated streams.
Prerequisites
- A Vibgrate Cloud workspace and an authenticated CLI (
vg login). - A project you can scan.
Step-by-step
Push results and attach a stable repository name with --repository-name:
vg scan --push --repository-name my-service
Use the same name every time you upload from that repository. A good convention is the canonical repo slug, for example org/my-service, so it stays unambiguous across your organization.
If you scanned earlier and want to push those artifacts under a name:
vg push --repository-name my-service
Why the name matters
Vibgrate Cloud charts DriftScore over time per repository. A consistent name is what lets the dashboard show a single, continuous trend line instead of many short ones. It is also the key used to roll repositories up into applications and portfolios.
Examples
From CI, set the name from your CI variables so it is always correct:
vg scan --push --repository-name "$CI_REPO_SLUG"
Related
After a repo is connected, see Map Repositories to Applications to group it into an app, View Drift Trends on the Dashboard to watch it over time, and Push Scan Results to Vibgrate Cloud for the upload basics.