118Wiki:Edit Summaries: Difference between revisions

→‎Why edit summaries are required: Adding note about minor edits
(Hmm... well, it's not just good practice it's expected in most circumstances!)
(→‎Why edit summaries are required: Adding note about minor edits)
 
Line 20: Line 20:
* A project’s long-term success rests (among other things) on its maintainability, and a maintainer has few tools more powerful than his project’s log. It’s worth taking the time to learn how to care for one properly. What may be a hassle at first soon becomes habit, and eventually a source of pride and productivity for all involved.
* A project’s long-term success rests (among other things) on its maintainability, and a maintainer has few tools more powerful than his project’s log. It’s worth taking the time to learn how to care for one properly. What may be a hassle at first soon becomes habit, and eventually a source of pride and productivity for all involved.
* Commit messages can adequately communicate why a change was made, and understanding that makes development and collaboration more efficient.
* Commit messages can adequately communicate why a change was made, and understanding that makes development and collaboration more efficient.
===Minor edits===
If you have made a small change on a page for spelling, grammar, or correcting a link or category, remember to tick '''"This is a minor edit"''' after writing your edit summary. This helps administrators and power users sort through high volumes of edits in the [[Special:RecentChanges|Recent changes]] page.


==What should be in an edit summary==
==What should be in an edit summary==