FAQ
Questions engineers ask
Short, honest answers. If yours isn't here, write to support@graftfork.com.
What happens if a carry gets stuck?
Sometimes a carry turns out harder than the report showed: upstream reversed something your change depends on, or a rewrite won't pass your tests. When that happens we stop the clock and tell you as soon as we know, with two options, and you choose.
More time, at the same price, with a date. Or a full refund of the $990 that day. You keep the report and anything we've already sent either way.
I can't finish this to the standard I promised in the time I quoted. Here's what's blocking it. Two ways forward, and it's your pick:
What counts as delivered?
A branch on the release you asked for, in a repository you choose, or a patch series. Every one of your changes is carried, dropped with a reason, rewritten, or settled by a decision you made, and your build and test commands add no failure that the new release doesn't already have. A person has read every rewrite. If we can't get there, it isn't delivered, and you get your money back.
How do refunds work?
If we can't deliver a carry we quoted, you get the full $990 back, by the same card, and you keep the report. Refunds are made by a person, not automatically, usually the same day you choose one. The exact terms are on the refunds page.
Do you work on private repositories?
Yes. Give us read access with a deploy key or a read-only token, or send a git format-patch export if you'd rather not grant access. See security for what happens to the code.
Do you need write access?
No. We never push to your repository unless you ask us to deliver the branch there.
Is the free report really the carry?
Yes. We run the carry on your fork and build and test it against the new release. The report shows what happened to every change, including anything that needs your decision.
How long does it take?
The free report usually takes a few business days. After payment, delivery is usually within a few business days too. If a carry is going to take longer, we tell you and you choose what happens next.
What if an agent gets a rewrite wrong?
That's why a person reviews every delivery. Several agents rewrite each broken change independently, and where they disagree we look closer. If a change needs a judgment only your team can make, it comes back to you as a question instead of a guess.
What kinds of forks work?
Any git repository where you keep your own commits on top of an upstream project, in any language. Quilt-style patch series, like Debian's, work too. Very large forks, Chromium-sized, need a conversation first.
How is this different from rebasing with rerere?
Rebase tells you what conflicts. It doesn't tell you which of your changes upstream already absorbed, which clean-applying changes landed next to upstream edits, or what to do about the conflicts. Graft answers those, and the report shows its reasoning for each one.
Can we run Graft ourselves?
Not today. Graft is a service: we run it, review the output and hand you the result. A hosted personal plan for individual copies is planned.
Who runs Graft?
One independent developer. See about.