commit-messages-guide

commit-messages-guide copied to clipboard

Hello. Doing some Git log archeology quite often, I always struggle to find **why** a commit was done rather than **what** it does: - a first line to summary **why**...

baby-gnu

I think this is wrong...If I understood well the guide haha. Mantieni la lingua in modo consistente Per i proprietari dei progetti: scegli una lingua e scrivi tutti i messaggi...

edoardottt

Include allcontributors.org to acknowledge the work of everyone

1

Reviewing translations is a valuable work. I'd like to be able to acknowledge and enhance this type of contribution. https://allcontributors.org/ https://github.com/all-contributors/all-contributors

RomuloOliveira

not follow the rules

3

Hi, Thanks for your great guide, but I am just curious that why you do not follow some of the rules in you commit messages? These should use the imperative...

esmaeilpour

As mentioned in #50 the whole project would have much more readability, if a TOC is added. Since it is easier for new readers to follow along the topics of...

twity1337

Use of Git Log and Status

1

Hi, Great guide! The source material gives a lot more context to this piece. You've covered every aspect on commits, but I think a little bit more emphasize on usage...

prkksh

I think it will be really helpful if some details about adding a git commit template was added. This way when they do `git commit` the editor will pop up...

menixator

url instead of issue number

1

I find in general a good practise to write in the commit message `Closes https://github.com/RomuloOliveira/commit-messages-guide/issues/32` Instead of `Closes #32` What do do you think? should we update this in the...

Ana06

Improvements

1

I really like the guide, it is really complete and I would like to link it from some of my projects. I think there is still place for some improvements....

Ana06

Translate to Bahasa

amiruddinid