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.

Totally - write commit messages with every one :) I was just wondering what makes a sensible commit - should it be a big job with 200 new lines of code, or a simple 2 line change/bug fix. I sometimes feel that I commit too often.

clinton3141
– clinton3141

2011-09-25 20:11:43 +00:00
Commented Sep 25, 2011 at 20:11
3

A single bug fix is for sure a single commit in my world. 200 new lines sounds a little much for me, I would commit when I have something working (and unit tested) to know I have committed the latest working codebase all the time.

Kristian
– Kristian

2011-09-25 20:16:45 +00:00
Commented Sep 25, 2011 at 20:16
1

I'd suggest to commit even more often. Some commits get no message, except for "fixup XXX" since they only contains small fixes for other commits not yet pushed.

maaartinus
– maaartinus

2011-10-15 13:42:40 +00:00
Commented Oct 15, 2011 at 13:42

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 »