CodeCargo logo

CodeCargo Documentation

Move to GitHub, and keep it clean

Plan your estate in waves, convert pipelines onto shared building blocks, and land every change as a pull request you approve. Once you're on GitHub, CodeCargo keeps your workflows on your guardrails, your network locked down, and your teams on the golden path.

Plan a migration

Migrate

Pipelines from Jenkins, Azure DevOps and GitLab move to GitHub Actions, and repositories from Azure DevOps, GitLab, Bitbucket Data Center and GitHub Enterprise Server move to GitHub. See what each source supports.

Migration Assistant

Import your pipelines and repositories, then migrate them in batches, with migration agents doing the conversion.

Migration Plan

Map the estate, decide where each project lands, group pipelines into families, and schedule the waves.

Prepare the Rewire

Fix references, then point Azure DevOps pipelines at their GitHub repositories, with each rebind approved and reversible.

Once You're on GitHub

Standardize

Group copied workflows onto shared building blocks, recover wasted Actions minutes, and climb the SLSA ladder.

Govern

Score every workflow against your guardrails and open pull requests that fix what fails.

Secure

See every outbound connection your workflows make, and block the ones you didn't approve.

Building Blocks

A private catalog of your approved workflows, actions and repository templates.

Self-service

Turn dispatchable workflows into forms anyone in your organization can run safely.

Understand

An always-current map of your services, owners, dependencies and the pipelines that ship them.

Agents

Agents

Govern every agent in your org, from CodeCargo jobs to GitHub Agentic Workflows and Copilot.

Dispatch

Ask for work in plain language. Dispatch plans it across agents and workflows, and runs it once you approve.

Agentic Jobs

Repeatable agent work on a schedule or on demand, with every run recorded for review.

How a Migration Runs

  1. See the whole estate. Connect your sources, and the Migration Plan maps every project and its repositories by destination, wave and how each one moves, before anyone commits to a date.
  2. Convert families, not files. Similar pipelines are grouped into pipeline families for review, and patterns that recur across jobs, such as shared-library functions and templates, become reusable Building Blocks. You review a handful of patterns instead of every translation.
  3. Ship in waves of pull requests. Schedule the waves, then migrate in batches. Each converted workflow arrives as a pull request, and nothing merges until you do.
  4. Cut over with approval. Prepare the Rewire fixes references and rebinds Azure DevOps pipelines to their GitHub repositories. Every rebind is approved first and can be rolled back.

Looking for something else? Check the FAQ or search with ⌘K.

Planning a move to GitHub?

Talk to us about scoping your migration, or see how our team can run it with you on Services. To try CodeCargo on the GitHub organization you already have, start free. Plans and pricing are at codecargo.com/pricing.