CI/CD for yourgo-to-market
Connect your GitHub repository. Every pull request gets a plan of what it will change, send and spend. Every merge deploys.
Cargo deployment preview
1 to create, 0 to update, 3 unchanged.
| Change | Resource | Kind | ID |
|---|---|---|---|
| Create | Inbound | play | play:inbound |
Cargo Successful in 6m, 1 resource(s) would change
lint / lint (pull_request) Successful in 18s
typecheck / typecheck (pull_request) Successful in 31s
From pull request to production
Every change goes through the pull request your team already reviews.
1. Plan
Cargo comments what a merge would change.
+ play inboundcreatesends, at most2,140credits, at most4,2802. Approve
Past a limit, a reviewer adds the approval label.
limit100 messageslabelapprove-impactcheck Cargopassed3. Deploy
Merging deploys it as a service user.
merge #128maindeploysuccessrun #1 Northwindto Alice4. Roll back
Revert and merge to put the workspace back.
revert #128mainplay inboundprevioussends already madekept
Ask @cargo to fix iton the pull request.
Mention @cargo in a review comment. A coding agent pushes the fix to the same branch and replies.
inbound-playSam
@cargo scoring still reads the old employee-count field. Fix it here.
Cargo
Fixed in a new commit on this branch. The plan comment is updated.
Connect a repository in three steps
Start from a Cargo project: cargo-ai project init creates one.
1. Install the Cargo GitHub app
Connect GitHub and install the app on the repository.
Settings → Connectors → GitHub2. Connect the repository
Pick the repository, the production branch and the project folder.
Settings → States3. Open a pull request
Cargo comments the plan. Turn off Deploy on push for plans only.
On GitHubQuestions people ask
Approvals, deletes, rollbacks and what still runs from a laptop.
Read the details
Each step above has its own page, with the commands and the limits.
Build the self-driving GTM engine
Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.