by Craig MerryCommunityKeep your changes to open-source projects on every new release, tested in a sandbox, and rebuild code blind from its spec.
graftfork keeps a changed copy of an open-source project (a fork, or a project with patched dependencies) on each upstream release. It moves your changes onto the release, runs the project's own tests in a sandbox, and keeps the moved branch only if every change lands and the tests pass. Otherwise the copy stays where it was and graftfork says why, so AgentOne can explain the stay, resolve a conflict file by file, or answer a question you decide.
It also rebuilds a program blind from its duramen record (a written spec with examples and, often, an oracle). Builders that never see the existing code write it in TypeScript, Python, Rust or Go, and graftfork keeps a rebuild only when every case of the record passes, plus hidden requests checked against the oracle. Every finished rebuild has a record signed by graftfork that anyone can check with npx graftfork verify-record.
With this connector AgentOne can:
Work that spends money (agent work on conflicts, rebuilds) states its price first and stays within limits you set, including a monthly cap per connected app. graftfork never changes your own branches: a move arrives on a branch of its own (graft/<release>), as a bundle you take or, if you choose, a pull request.
monday.com project management and CRM for projects, tasks, portfolios, boards, workflows, milestones, dependencies, forms, dashboards, cross-project portfolio status, and critical paths.
by monday.com
Access and create new content on Miro boards
by Miro
Automate workflows across thousands of apps via conversation
by Zapier