|
|
|
|
|
by majormajor
2199 days ago
|
|
I'm picturing 1 to 2 minutes on the message, which is why I don't see it as competing with refactoring or test time. I also think spending paragraphs on "commit message standards" is overkill. I don't care about full stops or capitalization or anything, I just want to know some basics: "What is this fixing or adding. Why is it done this way. Are there any special considerations that kept it from being done a different way?" You bring up a good point about location, too; i don't particularly care if the info is in a ticket or commit message or a pull request, as long as I can get to it) |
|