Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Rule of thumb for you: if you have two consecutive commits with identical messages, you're almost certainly doing it wrong. Either they should be one commit, or you should figure out what's different about them and write log messages that reflect that difference (e.g. "define new paint data" and "set paint data properly" rather than "working on paint system" x2).

Marnen Laibow-Koser
– Marnen Laibow-Koser

2018-05-16 16:43:14 +00:00
Commented May 16, 2018 at 16:43

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »