View the Nessie commit log and transplant selected commits to another branch
domain: projectnessie.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
View the commit log in the CLI: LOG ON my_branch (or LOG to see the current branch log); the output includes commit hashes, author, timestamp, and commit message
Identify the commit hashes you want to cherry-pick
Transplant (cherry-pick) selected commits to a target branch: CHERRY-PICK ON target_branch COMMITS hash1, hash2
Using the REST API: POST /api/v2/trees/{targetBranch}/history/transplant with a JSON body listing hashesToTransplant and the fromRefName
Verify the transplanted commits appear on the target branch's log
Known gotchas
Transplant in Nessie is analogous to git cherry-pick, not rebase; it replays the content changes introduced by each listed commit onto the target branch
Commits must be listed in chronological order (oldest first) when transplanting; reversing the order can produce unexpected content states
If a transplanted commit references a content key that does not exist on the target branch, the key is created; if it conflicts with an existing key on the target branch, a conflict error is raised
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?