S
S
sorry_i_noob2018-05-22 22:20:04
git
sorry_i_noob, 2018-05-22 22:20:04

Is it bad that I have some commit-messages in Git that are not very meaningful? And in general, these messages are only important when I do a push? Or always?

Is it bad that I have some commit-messages in Git that are not very meaningful? And in general, these messages are only important when I do a push? Or always (that is, the most common commits that are only on my computer are also important and should be as meaningful as possible)?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
V
Vitaly, 2018-05-22
@sorry_i_noob

If there is any issue tracker, then the main message should contain the ticket number. The main message should not be longer than 72 characters (as well as the length of lines in general). After the main message, there is an empty line and then a detailed commit text (if needed). The main message should be as informative and capacious as possible, detailed text can be written in free form. Each commit should commit a small but completed piece of work. There can be many commits within one task.

D
Dmitry, 2018-06-05
@dlnsk

If the content of the messages does not suit you, then you can always do git rebase -iand rename them, or even merge something together. Naturally, this must be done beforegit push

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question