DNA: started from roll-back.md

Root ·

Started from docs/dna/roll-back.md in the Knowen repository: How Knowen works is kept with the code.

Changes to the content

# Roll back a merge
⏎
**Goal:** undo a merge, or part of it, in the public graph.
⏎
**Before you start:** the owners of what the merge changed can roll back their part; the writer can roll back their own merge, and Root anything.
⏎
1. Open the merged proposal (from **Publishing**, **Reviewing**, or the node's history) and go to **Changes**.
2. Click **Roll back…**.
3. Tick the changes to undo. Each says whether it can still be rolled back; a change that someone edited since is a conflict and is left as it is unless you restore it on purpose.
4. Say **Why roll back?**: the writer is told, and the reason goes in the review log and each node's history.
⏎
   ![Roll back the merge of “Waves”: the changes still in the public graph, and why](media/roll-back.webp)
5. Click **Roll back selected**.
⏎
**What happens next.** Edited nodes get their earlier text back as a new version. New nodes go to the Trash, with whatever hangs only from them. New connections are removed. A writer whose edit was rolled back is no longer an owner of that node.
⏎
**Undo.** Nothing is erased: **Re-apply** on the proposal puts rolled-back changes back.
⏎
# Parents
⏎
* A proposal's life
* History, versions and rollback⏎

Feedback00

No feedback yet. Say whether this change improves the node.

Sign in to add a new comment.