Depot CI is now available in Entire

Today, Entire is launching its new Git forge publicly with Depot CI as one of its suggested CI providers on day one. You can connect Depot to your Entire project and migrate your existing GitHub Actions workflows to run on Depot CI without any need for GitHub.

What you get

Depot CI is our own programmable CI engine. It speaks GitHub Actions workflow syntax, but everything underneath is ours: the orchestrator, the compute, the caching, and the APIs. It's faster and more reliable than GitHub Actions, as it is our own custom-built CI engine that is designed to run workflows at machine scale.

Connect from Entire or Depot: install the Depot plugin from Entire and choose the Depot organization to connect, or open Settings > Depot CI > General in Depot and click Connect Entire under Connections. Follow the installation flow in Entire, then return to Depot to run your workflows.

Bring your existing GitHub Actions workflows: depot ci migrate --forge=entire copies your workflows from .github/workflows/ into .depot/workflows/, applying Depot CI compatibility fixes, and copies local actions into .depot/actions/. Entire migration requires Depot CLI v2.103.3 or later.

Manage your secrets and variables: add the secrets and variables your workflows need from the dashboard or the CLI. If they're stored in GitHub, import them with depot ci migrate secrets-and-vars from a checkout whose push remote points to that GitHub repository.

Runs triggered by Entire events: branch and tag pushes in Entire repositories trigger matching Depot CI workflows. No separate webhook setup, no GitHub round trip.

Status checks back in Entire: workflow and job results are visible on branch commits in Entire, with links to the results in Depot. Runs on tags appear only in Depot.

Everything else Depot CI already does: logs, CPU and memory metrics, SSH into a job, retries of individual failures, custom runner images, and a first-class API and CLI so agents can trigger runs and read results without a git event.

Get a faster and more reliable CI experience without GitHub, and without having to learn a new workflow syntax. Depot CI connects directly to your Entire repository and supports GitHub Actions workflow syntax. We run your workflows on our own infrastructure for better performance and reliability.

Getting started

You'll need an Entire account with a repository.

You'll also need permission to install the Depot plugin for your Entire project and ownership of the Depot organization you connect.

Create a new repo

Follow the Entire repository guide to create a repository. If you already have one, connect its Entire project to Depot.

Connect Depot to Entire

1. Open Settings > Depot CI > General in Depot.
2. Under Connections, click the Connect Entire row.
3. Follow the installation flow in Entire to install the Depot plugin for your project.

That's it. You'll start on the Depot CI page in your dashboard, ready for your first run.

You can also begin from the Depot plugin in Entire and select the Depot organization to connect. To review or manage the connection afterward, return to Settings > Depot CI > General. Your project appears under Connections with the label Connected through Entire.

Migrate your workflows

Run migration from a checkout whose git remote points to your Entire repository.

1. Install Depot CLI v2.103.3 or later.
2. Run depot login and select the connected organization with depot org switch <org-id>.
3. Run depot ci migrate --forge=entire. It checks repository access and copies your workflows and local actions into .depot/ with compatibility fixes.
4. Review the workflows against the Depot CI compatibility reference and Entire limitations. Use a push trigger for branch changes; triggers for Entire trails are coming soon.
5. Add the secrets and variables your workflows reference through the dashboard or CLI. If they're stored in GitHub, run depot ci migrate secrets-and-vars from a checkout whose push remote points to that GitHub repository. Depot can't import secrets and variables from Entire.
6. Commit the files in .depot/ and push them to your Entire repository to start a run.

See the Entire integration docs for a complete first workflow and scheduled or manual runs.

See your first run

Runs show up on the Depot CI page in your dashboard, or you can list them from the CLI. Install the Depot CLI, run depot login, and select the connected organization with depot org switch <org-id> first:

depot ci run list
depot ci status <run-id>

The bottleneck has moved from writing code to everything after

As we continue to talk about, the landscape of software engineering is changing rapidly. With it, the primitives of software delivery are changing too. The bottleneck has moved from writing code to everything after: integrating it, testing it, and deploying it.

We've spent the past four years making the delivery loop faster, one primitive at a time: container builds, then GitHub Actions runners, then caching and registries, then our own CI engine.

CI is changing and the software delivery loop as a whole requires rethinking things through the lens of what it looks like for a 10-person engineering team to be operating a lot more like a 1,000-person engineering team. Agents and AI are fundamentally increasing the velocity of engineering teams at a growth rate that is significantly faster than the growth of the teams themselves.

Depot CI is built for this world. It is designed to run workflows at machine scale, and it is fully API-driven so that agents can trigger runs, read logs, and act on failures without a human clicking through a dashboard. You can bring your existing GitHub Actions workflows to Depot CI, and you can migrate your secrets and variables from a GitHub repository in one command. It is faster and more reliable than GitHub Actions, and it is now available as a first-class CI provider in Entire.

Pricing

All Depot plans include a bucket of Depot CI minutes. After that, you pay for what you use. See plans and Depot CI pricing on the pricing page.

Learn more

Tell us what's working and what you'd like next in our Discord community, or reach out through Depot support.

• Entire integration docs
• Entire launch announcement
• Depot CI overview
• GitHub Actions compatibility