![[Home]](/static/logo.png){kind=logo}
The ability to collect a number of changes into one RecentChanges entry, revocable as a group, or in pieces.
Good for describing proposals.
Suppose a person is installing an ad-hoc navigation bar between 5 pages:
| page 1 | page 2 | page 3 | page 4 | page 5 | ||||||
By making it one change item, it only appears once in RecentChanges, and can easily be rolled back if need be.
Refactorings frequently involve multiple pages. Atomic commits would make it so that the refactoring deltas can be considered together, and rolled back easily as a group, or individually, if that needs to be the case.
Perhaps you hit a button labeled “Begin Grouping Changes,” then go around making changes, and then pressing “End Grouping Changes.” You write a master summary (wrapped around the ending summaries) of the change, hit the final submit button, and the master change summary appears in RecentChanges.
Revoking individual pages would probably consist of just applying changes on top of the atomic change.
A related idea is TestBranches (#12).
EditMerging collects multiple edits by a single person to a single page. AtomicCommits generalizes this to multiple pages.