---
title: "Deploys & Repos"
section: "Deploys & Repos"
description: "Deploys & Repos shows which version of each service runs in each environment and whether a pipeline tested it after the deploy. Your CI reports deploys."
url: https://docs.smartestqa.ai/en/deployments.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "deploys repos deployments repositories environments versions commit sha tested after deploy ci webhook deploy token github gitlab bitbucket azure devops gitea"
---
# Deploys & Repos

Deploys & Repos answers two questions per service and environment: which version is running, and did a pipeline test it after it was deployed? Your CI tells SmartestQA about each deploy; SmartestQA matches it with the pipeline runs that followed.

## In short

**On this page you can**

- See the version (commit and tag) each service runs in DEV, TEST, PRP and your own environments.
- Spot deploys that no pipeline tested, shown as Not tested .
- Open a deploy to read its commits, changed files and the pipeline runs after it.
- Connect GitHub, GitLab, Bitbucket, Azure DevOps or Gitea repositories, with or without a token.

**How to use it**

1. Open Repositories and click Add repository .
2. Copy the deploy token and the CI step from CI code & deploy token .
3. Add the step after your deploy step in CI and run one deploy.
4. Run a pipeline in the same environment, then check Currently running versions .

**At a glance**

- **Where:** Main menu › **Deploys & Repos**. Tabs: **Overview** and **Repositories**.
- **Who:** [Admins](https://docs.smartestqa.ai/en/company-settings-roles.html) and Users with access to the project. Admins also see the repositories under **[Integrations](https://docs.smartestqa.ai/en/integrations.html)**.
- **You need:** A Git repository URL and a CI system that can send an HTTP request after a deploy. A read-only token is optional.
- **Time:** About 10 minutes: add the repository, store the deploy token in CI, add one step.
- **Produces:** **Deploy records** per service and environment, with the previous version, commits and the [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) runs that tested it.
- **Used by:** The KPI cards on this page and **[Autonomous Agents](https://docs.smartestqa.ai/en/ai-agents.html)** that start when a deploy succeeds.
- **Project types:** The same for WEB, MOBILE and DESKTOP projects. A deploy is matched with pipeline runs by environment, not by project type.

## Start from your question

I want to…

- [Connect a repository](https://docs.smartestqa.ai/en/deployments-repos.html#add-repo)
- [Send deploys from my CI](https://docs.smartestqa.ai/en/deployments-ci.html#add-ci-step)
- [See what runs where](https://docs.smartestqa.ai/en/deployments-overview.html#current-versions)
- [Read the commits of a deploy](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail)
- [Replace a leaked deploy token](https://docs.smartestqa.ai/en/deployments-ci.html#regenerate)

Something is wrong

- [CI gets 401 from the webhook](https://docs.smartestqa.ai/en/deployments-troubleshooting.html#fix-invalid-token)
- [A deploy stays “Not tested”](https://docs.smartestqa.ai/en/deployments-troubleshooting.html#fix-not-tested)
- [I see “No pipeline environment”](https://docs.smartestqa.ai/en/deployments-troubleshooting.html#fix-no-pipeline-env)
- [The commit list is empty](https://docs.smartestqa.ai/en/deployments-troubleshooting.html#fix-commits-need-token)
- [All Deploys & Repos problems](https://docs.smartestqa.ai/en/deployments-troubleshooting.html)

How does it work?

- [Which runs count as “tested after”](https://docs.smartestqa.ai/en/deployments-numbers.html#tested-window)
- [How the four KPI cards are counted](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards)
- [What each cell colour means](https://docs.smartestqa.ai/en/deployments-numbers.html#cell-states)
- [What happens when CI sends “started” first](https://docs.smartestqa.ai/en/deployments-ci.html#started-then-success)
- [Token or notification only?](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes)

## Where Deploys & Repos fits

The main menu is the order of work. Deploys & Repos sits beside it: it does not create tests. It watches what reaches each environment and checks whether the [pipelines](https://docs.smartestqa.ai/en/schedule-create.html) you built in **Schedule** ran against it afterwards.

1. **Discover** — Pages, controls, rules
2. **Analyze** — [Requirements](https://docs.smartestqa.ai/en/analyze-requirements.html)
3. **Automate** — Test cases
4. **Schedule** — Pipelines per environment
5. **Report** — Results of each run
6. **Maintenance** — Heal and review

A deploy record comes from your CI. The “tested after” state comes from pipeline runs in Schedule. A click on a run opens it in Report. A failed run can become a task in [Tasks](https://docs.smartestqa.ai/en/tasks.html).

## Why use it

- **You see untested releases.** A cell turns amber with **Not tested** when a version reached an environment and no [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) ran there since.
- **You know what changed.** With a token, each deploy lists the commits and changed files since the previous successful deploy in the same environment.
- **Several services, one view.** A project can have many repositories (web, api, auth…). Each one is a row; each environment is a column.
- **Agents can react to deploys.** Every successful deploy is passed to [Autonomous Agents](https://docs.smartestqa.ai/en/ai-agents.html), so an agent can run checks right after a release.
- **It never blocks your release.** The CI step ends with `|| true`: if SmartestQA cannot be reached, the deploy still succeeds.

## The building blocks

- **Repository:** A Git repository connected to the project, for example `https://github.com/acme/web-frontend`. It has a provider, a [service name](https://docs.smartestqa.ai/en/deployments-repos.html#fields), an optional access token and an environment mapping.
- **Service name:** The short key deploys are shown under, such as `web` or `api`. Unique in the project.
- **Environment:** Where a version runs: DEV, TEST, PRP, or a name you add such as STAGING. [Pipeline](https://docs.smartestqa.ai/en/schedule-create.html) runs carry DEV, TEST or PRP.
- **Environment mapping:** Which environments you expect this repository in, with an optional branch and start URL for reference. It decides which cells show [**Not mapped**](https://docs.smartestqa.ai/en/deployments-overview.html#cell-content).
- **Deploy token:** A secret that starts with `sdt_`. It lets your CI record deploys for one repository and nothing else. [More](https://docs.smartestqa.ai/en/deployments-ci.html#deploy-token).
- **Access token:** An optional read-only token for your Git provider. With it, SmartestQA reads commits and changed files between two versions. [More](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes).
- **Deploy:** One record: repository, environment, commit SHA, status (**Succeeded**, **Failed**, **In progress**, **Cancelled**), version, branch, who deployed it and a link to the CI run.
- **Tested after:** The pipeline runs in the same environment that started after a successful deploy and before the next one. [Formula](https://docs.smartestqa.ai/en/deployments-numbers.html#tested-window).

## The screen

![Deploys & Repos › Overview.](https://docs.smartestqa.ai/media/shots/DEP-SHOT-01.png)

- **Refresh** (icon, top right): reloads the cards, the grid and the history.
- **KPI cards**: [**Connected repositories**](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards), [**Deploys in last 7 days**](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards), [**Tested after deploy**](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards), [**Running untested**](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards). [How they are counted](https://docs.smartestqa.ai/en/deployments-numbers.html#kpi-cards).
- ****Overview** tab**: [**Currently running versions**](https://docs.smartestqa.ai/en/deployments-overview.html#current-versions) (one row per service, one column per environment) and [**Deploy history**](https://docs.smartestqa.ai/en/deployments-overview.html#history).
- ****Repositories** tab**: [**Code repositories**](https://docs.smartestqa.ai/en/deployments-repos.html#add-repo), where you add, change and delete repositories and get the CI code.
- **Deploy detail**: click a cell or a history row to open the side panel.

| Area | What it is for | Go there when |
| --- | --- | --- |
| [Currently running versions](https://docs.smartestqa.ai/en/deployments-overview.html#current-versions) | The last successful deploy per service and environment, with its test state. | Before a release decision, or to see what a tester is testing. |
| [Deploy history](https://docs.smartestqa.ai/en/deployments-overview.html#history) | Every deploy record, newest first, filterable by environment, service and period. | You look for a failed or cancelled deploy, or for who deployed what. |
| [Deploy detail](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail) | Previous version, commits, changed files and the [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) runs after the deploy. | A run went red and you want to know what changed. |
| [Repositories](https://docs.smartestqa.ai/en/deployments-repos.html) | Connections, environment mapping, deploy token and CI code. | You set up a new service or rotate a token. |

No project selected? The page shows “Select a project from the header to manage its agents.” Pick a project in the header.

## Before you start

| You need | Why | Check it |
| --- | --- | --- |
| The repository URL | To create the connection and build commit links. | It opens in your browser and contains owner and repository. |
| Access to your CI settings | To store the deploy token as a secret and add one step. | You can add a secret or credential to the [pipeline](https://docs.smartestqa.ai/en/schedule-create.html). |
| Pipelines in Schedule that run per environment | Only pipeline runs count as “tested after”. | Your pipeline’s environment is DEV, TEST or PRP. |
| Optional: a read-only Git token | To see commits and changed files. | See the token types in [Connection modes](https://docs.smartestqa.ai/en/deployments-repos.html#connection-modes). |

## Best practices

#### Do

- Use one repository per deployable service, with short service names (`web`, `api`).
- Send the same environment names your [pipelines](https://docs.smartestqa.ai/en/schedule-create.html) use: DEV, TEST, PRP.
- Send the full commit SHA and, if you tag releases, the tag as `version`.
- Run a pipeline in that environment after every deploy, for example a smoke pipeline.
- Use a fine-grained, read-only token when you connect with a token.

#### Don’t

- Paste the deploy token into CI code. Store it as a secret.
- Give the access token write rights. Reading is enough.
- Report deploys to environment names no pipeline uses, unless you only want the version record.
- Reuse one repository record for two services: the deploys would mix in one row.

## In this section

- [Connect a repository](https://docs.smartestqa.ai/en/deployments-repos.html) — Add, change and delete code repositories: provider, service name, token or notification only, test connection and environment mapping.
- [Send deploys from CI](https://docs.smartestqa.ai/en/deployments-ci.html) — The deploy token, the webhook URL and payload, ready-made CI steps, and what SmartestQA does with each notification.
- [Versions, history and deploy detail](https://docs.smartestqa.ai/en/deployments-overview.html) — Read the Currently running versions grid, filter the Deploy history and open a deploy to see its commits and the runs that tested it.
- [How the numbers work](https://docs.smartestqa.ai/en/deployments-numbers.html) — Formulas and worked examples for the KPI cards, the tested-after window, the cell states, the untested streak, commit counts and relative times.
- [Troubleshooting](https://docs.smartestqa.ai/en/deployments-troubleshooting.html) — Every Deploys & Repos message and symptom, with why it happens, what to check and how to fix it.
- [FAQ, MCP & limits](https://docs.smartestqa.ai/en/deployments-faq.html) — Questions and answers, what AI assistants and agents can do with deploys, and the module’s limits.

## Related

- [Start pipelines from CI/CD](https://docs.smartestqa.ai/en/integrations-cicd.html)
- [Autonomous Agents that react to deploys](https://docs.smartestqa.ai/en/ai-agents.html)
- [Pipeline environments](https://docs.smartestqa.ai/en/schedule-where.html#environment)
- [Report](https://docs.smartestqa.ai/en/report.html)
- [Webhooks](https://docs.smartestqa.ai/en/integrations-webhooks.html)
