Connecting and Managing Repositories

Overview

Everything in StretchDev hangs off a project — a repository you've connected. A project records the repo's name, URL, default branch, primary language, and an optional custom quality-gate policy, and it owns all the scans and issues produced against it. This article covers creating, editing, and deleting projects.

Connect a repository

1. Open the Projects tab and click New.
2. Fill in the fields:
- Name (required) — a human-readable label, for example Billing API.
- Repository URL — where the code lives, for example https://git.example.com/billing-api.
- Default branch — the branch scans target by default. Leave blank to use main.
- Primary language — the main language of the repo (JavaScript, TypeScript, Python, Go, Rust, and more). This drives syntax highlighting in file views and the default file layout.
- Quality gate (optional) — a custom policy of pass/fail conditions. Leave it empty to use the default gate. See Configuring quality-gate policies for the JSON shape.
3. Click Save. The project appears in the table immediately with a generated key like proj-4f2a9c8b1d0e, and it is scoped to your organization automatically — you never pass an organization ID yourself.

Only the name is strictly required; you can add the URL, branch, language, and gate later.

Edit a project

1. In the Projects table, open the project (or click Edit on its row).
2. Update any field — name, repository URL, default branch, primary language, or the quality-gate policy.
3. Click Save. Changes apply to future scans; existing scans keep the results they were recorded with.

Editing is a partial update: fields you leave untouched keep their current values, so you can change just the default branch without re-entering everything else.

Delete a project

1. Open the project you want to remove.
2. Click Delete and confirm.
3. The project is removed from your workspace. This also removes the project's association with its scans and issues, so delete only when you're sure you no longer need that history.

Warning: Deleting a project is permanent. If you only want to stop scanning a repo for a while, simply stop running scans against it rather than deleting the project.

Example

Your team splits a monolith into two services. You:

1. Edit the existing project Platform — change its name to Platform (legacy) and leave its history intact.
2. Create two new projects, Orders Service and Inventory Service, each with its own repo URL, main default branch, and language Go.
3. Attach a stricter gate to Orders Service because it handles payments.

Now each service is scored independently, and the Dashboard reflects three projects.

Tips

• Use clear, consistent names — they appear throughout Scans, Run history, and the Dashboard.
• Set the primary language accurately; it controls how file snippets and ratings are presented.
• Point default branch at the branch you actually release from so scans default to the right target.
• You can look up any project by its generated key or by its ID — both work anywhere a project is referenced.

Troubleshooting

• "A project name is required." The name field was empty. Enter a name and save again.
• "Project not found." The project ID or key doesn't match a project in your organization. Confirm you're in the right workspace and that the project wasn't deleted.
• A project I expect isn't listed. Projects are tenant-scoped; you only see projects owned by your current organization.