Orbox
Waitlist
All examples
Engineering

Shipping a new release

How one team described it:
“After a merge in GitHub the tests run, we deploy to staging on Vercel, QA signs off in Linear, the lead approves the release in Slack, we ship to production and send customers a changelog.”
  • GitHub Actions
  • Vercel
  • Linear
  • Slack
  • Sentry
  • +2
6 run on their own2 stay with people

Typically saves 3–4 h per release

Make this process yours

Orbox starts from this example and asks how your team does it.

No developer? Work with an Orbox Partner
EngineeringShipping a new release
Process description
Trigger
A change is merged into the main branch in GitHub
Outcome
The new version is live, verified, and customers know what changed.
Tools
GitHub ActionsVercelLinearSlackSentryNotionIntercom
Steps
  1. 1
    Run automated testsDeveloper, tool GitHub Actions
    Can be automated
  2. 2
    Deploy to stagingDeveloper, tool Vercel
    Can be automated
  3. 3
    QA sign-offQA, tool Linear
    Stays with a person
  4. 4
    Approve the releaseHead of engineering, tool Slack
    Stays with a person
  5. 5
    Deploy to productionDeveloper, tool Vercel
    Can be automated
  6. 6
    Watch for errors after releaseDeveloper, tool Sentry
    Can be automated
  7. 7
    Write the changelogProduct, tool Notion
    Can be automated
  8. 8
    Announce to customersProduct, tool Intercom
    Can be automated

Want this process in your company?

Make this process yours

Orbox starts from this example and asks how your team does it.

No developer? Work with an Orbox Partner

More examples