---
title: "Git, CI and deploy"
description: "Host repositories, run pipelines and ship releases on Overlane itself, with GitHub, Vercel, Netlify and Fly as optional connections."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Git, CI and deploy

Overlane hosts your code, runs your tests and deploys your releases, so a project needs no third-party account to go from a first commit to production. GitHub, Vercel, Netlify and Fly are connections you can add; nothing here requires one.

Each part is deterministic code first: pipeline files are validated with line-cited errors before they run, path filters and affected-test selection are plain rules, secrets are masked by value, and a deploy checks an artifact digest before anything leaves. No model is on the path.

- [Repositories and pull requests](/git-ci-deploy/repos-and-pull-requests/): create a repository, branch, push, open a pull request, review it and merge, with roles and protection enforced on the server.
- [Import and mirror from GitHub](/git-ci-deploy/import-and-mirror/): copy a GitHub repository or mirror it with exactly one writable side, and what happens when history is rewritten.
- [Pipeline file reference](/git-ci-deploy/pipeline-reference/): every key of `.overlane/ci.yml`, how jobs are routed, and how errors cite the line.
- [Caching, flaky tests and CI cost](/git-ci-deploy/caching-and-flaky-tests/): cache keys, the one re-run for a failing test, cancelling superseded runs, affected tests and the per-pull-request cost gate.
- [Secrets, fork pull requests and egress](/git-ci-deploy/secrets-forks-and-egress/): what a job can read and reach.
- [Environments and previews](/git-ci-deploy/environments-and-previews/): targets, environments, a preview per branch and the connectors.
- [Rollback and approvals](/git-ci-deploy/rollback-and-approvals/): one-command rollback, failed deploys, protected environments and artifact digests.

A repository stays optional. A project created in onboarding is a real project with tasks, memory and evidence before it has one, and the repository attaches when you want it.

```sh
overlane repo status
overlane repo create app
overlane ci validate
```

`repo status` says whether native repositories are available on your deployment right now and whether one is offered by default; when the git host is not provisioned it says so, and the project keeps working without a repository.

Command reference: [repo create](/cli/repo-create/), [repo import](/cli/repo-import/), [ci run](/cli/ci-run/), [ci validate](/cli/ci-validate/), [deploy run](/cli/deploy-run/) and [deploy rollback](/cli/deploy-rollback/).

Source: https://docs.overlane.app/git-ci-deploy/index.mdx