|
|
|
|
|
|
by mAritz
2622 days ago
|
|
|
I think a good way to look at it is to think of "explain why" in commit messages as explaining why the code was changed from the previous state to the new state. This may need explanations on how some of the code works, but it doesn't have to. The "explain why" that explains how the current code state works however should sit next to the current code. |
|
|