Post AVHdKaUChHWDhtHDfM by ParadeGrotesque@mastodon.sdf.org
 (DIR) More posts by ParadeGrotesque@mastodon.sdf.org
 (DIR) Post #AVHdKaUChHWDhtHDfM by ParadeGrotesque@mastodon.sdf.org
       2023-05-03T16:28:42Z
       
       0 likes, 0 repeats
       
       All right Mastodon, question time!🐘 Multi-line git commit messages, Yea or Nay? And why, or why not?(Feel free to expand in the replies/comments)
       
 (DIR) Post #AVHdfGftYCc2LObesK by penguin42@mastodon.org.uk
       2023-05-03T16:32:20Z
       
       0 likes, 0 repeats
       
       @ParadeGrotesque Hell yes; a commit message should explain why you're making the change, if it changes a command line/file layout then include an example of the new format, if it is a performance thing include some numbers.
       
 (DIR) Post #AVHhScuHyqRBLdZCBk by khm@mastodon.sdf.org
       2023-05-03T17:14:58Z
       
       0 likes, 0 repeats
       
       @ParadeGrotesque one line summary followed by two line breaks and a detailed rationale for the changes... in any source control system, not just git!
       
 (DIR) Post #AVHjXZfVeE6Wf18mdU by pro@mu.zaitcev.nu
       2023-05-03T17:38:15.588598Z
       
       0 likes, 1 repeats
       
       @penguin42 @ParadeGrotesque In addition, the first line is typically a capsule summary.Now let's have a poll about the permissible line length in commit messages.
       
 (DIR) Post #AVHjbdB4XjUWhaq2BE by penguin42@mastodon.org.uk
       2023-05-03T17:38:56Z
       
       0 likes, 0 repeats
       
       @pro @ParadeGrotesque Vt100-w is enough for anyone.
       
 (DIR) Post #AVHqlbcRtKrERZLZQ0 by coderCyclist@infosec.exchange
       2023-05-03T17:42:34Z
       
       0 likes, 0 repeats
       
       @ParadeGrotesque If all of my teammates reliably entered adequate commit subjects in the first line, I would be totally OK with multi-line messages. Unfortunately, some of them only put the ticket number in the first line and the Azure DevOps web UI only shows the first line of each message in the commit history. 🤦‍♂️
       
 (DIR) Post #AVHr8stLq2mcfrLwbQ by ParadeGrotesque@mastodon.sdf.org
       2023-05-03T19:03:25Z
       
       0 likes, 0 repeats
       
       @coderCyclist I feel your pain.Especially since you are working on Azure.
       
 (DIR) Post #AVHvthwYlFPa96R6rg by tseitr@mastodon.sdf.org
       2023-05-03T19:56:41Z
       
       0 likes, 0 repeats
       
       @ParadeGrotesque "fixed vars"
       
 (DIR) Post #AhuZerVQZatKulvGjo by neon@fedi.neon.moe
       2023-05-03T16:33:02.496216Z
       
       0 likes, 0 repeats
       
       @ParadeGrotesque The first line should definitely always be a good summary, but I think it's sometimes good to provide further context or explain a particularly arcane-looking change.