Skip to content
Latchkey

Depot: Repository Must Be Owned by a GitHub Org

Depot runners require a GitHub organization. Repositories under a personal account are not eligible, which is a common reason a first job never picks up.

Per Depot's docs, to use Depot GitHub Actions runners "your repository must be owned by a GitHub organization (not a personal account)." This is the first thing to check when a brand-new setup will not schedule. This page covers connecting the org and the setup path, attributed to depot.dev/docs/github-actions/overview and the quickstart.

Why personal-account repos do not work

Depot documents that the repository must be owned by a GitHub organization. A repo under a personal account cannot receive Depot runners, so its jobs will stay queued no matter how the runs-on label is set. Fix: transfer the repository into a GitHub organization, then connect Depot to that org.

Connect the org (documented steps)

  • Log into your Depot dashboard.
  • Select GitHub Actions.
  • Click Connect to GitHub to open the installation form.
  • Install and authorize the Depot app for the organization.

Organization owner and approval

Per Depot's quickstart, organization owners must complete this setup, and some organizations require administrator approval before runners become active. If a non-owner attempts the connection, or approval is pending, runners will not serve jobs yet. Fix: have an org owner complete the install and clear any pending admin approval.

When the real problem is flaky failures, not setup

If your Depot jobs are picked up and fast but still fail intermittently on out-of-memory kills, disk-full errors, or registry timeouts, no runner-speed tuning removes that class of failure. Latchkey is also a drop-in managed runner reached by a runs-on label swap, but it is built around self-healing CI: it detects, diagnoses, fixes, and retries transient and mechanical failures automatically, and lists up to 58% lower per-minute cost than GitHub Actions. If troubleshooting keeps landing on flaky re-runs, it is worth piloting one workflow on Latchkey next to Depot and comparing.

Frequently asked questions

Can I use Depot runners on a personal GitHub repo?
No. Depot's docs state the repository must be owned by a GitHub organization, not a personal account. Transfer the repo into an org first. Verify at depot.dev/docs/github-actions/overview.
Who can connect the org to Depot?
Per Depot's quickstart, organization owners complete the setup, and some organizations require administrator approval before runners become active.

Related guides

See what you would save - Latchkey managed runners with self-healing. Start free →