graft
Get a free report

Docs

Getting started

Graft is a service: there's nothing to install. You tell us about your fork, we send a free report, and if you want the carried branch, we deliver it. Here's each step and what it needs.

The request flow

Five messages, from your request to a branch you can merge. The only payment happens after you've read the report and asked for the branch.

Every customer email comes from Craig, and you can reply to any of them with questions.

You and Graft
You
Graft
Fork URL, upstream, target releasethe form, 2 minutes
Free report: every change, built and testeda few business days
"We want the branch", plus your decisionsreply to the email
Payment link, $990by email
PaymentStripe checkout
Branch, report, decisions lista few business days
One payment, after the report. Nothing is due if you stop after the report.

What we need from you

  1. Your fork

    A repository URL, such as github.com/your-org/envoy, and the branch you keep your changes on if it isn't the default. For a private fork, read access with a deploy key or a read-only token, or a patch export:

    git format-patch <the upstream release you're on>..<your branch> -o graft-export/

  2. The upstream and the release you want

    The upstream repository, and the release to carry onto. Leave the release blank and we use upstream's latest.

  3. How you build and test

    Optional, but it makes the report much more useful: the commands that build your project and run the tests that cover your changes. We run them on the new release alone and with your changes on, and compare.

What you get back

  • A branch on the new release, in a repository you choose, or a patch series you apply yourselves. Your CI runs on it like any other branch.
  • A report with one line per change: carried, dropped with the reason, rewritten, or waiting on you. It also lists what wasn't carried and why, such as your fork's own CI files.
  • A decisions list at the top: anything only your team can decide, with each option built and tested so you can see what it costs. You answer on the report page.
  • Build and test results for each command: pass, already failing upstream, broken by the carry, fixed by the carry, or timed out.

Timelines

  • Free report: usually within a few business days of your request.
  • Delivery: usually within a few business days of payment..
  • Replies: within two business days, by email.
  • If it's going to take longer: we tell you as soon as we know, and you choose more time or a full refund.

Your report page

Each report has its own private link, sent to you by email. To see all your carries, sign in with the address your reports go to; we send a one-time link, and there's no password.

Next steps

Request a free report, read how a carry works, or see how we handle your code.