en:git

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
en:git [2026/04/02 09:17] – [Introduction to Git and GitHub for Musicology Editorial Work] martinen:git [2026/04/03 09:40] (aktuell) – Add some notes about imperative mood in Git messages piasteuck
Zeile 231: Zeile 231:
  
 <code bash> <code bash>
-git commit -m "Corrected note durations in motet_01"+git commit -m "Correct note durations in motet_01"
 </code> </code>
  
Zeile 240: Zeile 240:
  
 Good examples: Good examples:
-  * ''Corrected mensuration encoding in Kyrie'' +  * ''Correct mensuration encoding in Kyrie'' 
-  * ''Normalized staff labels in source B'' +  * ''Normalize staff labels in source B'' 
-  * ''Fixed barline errors in movement 3'' +  * ''Fix barline errors in movement 3'' 
-  * ''Added editorial note on unclear accidentals''+  * ''Add editorial note on unclear accidentals'' 
 + 
 +You may wonder why the grammar in these sentences seems a bit odd.  
 + 
 +Most projects follow a common convention for commit messages: the subject line is written in imperative mood, as if giving an instruction. So "Add," "Fix," "Remove" rather than "Added" or "Fixes." 
 + 
 +A helpful trick to check: your message should complete the sentence //"If applied, this commit will ..."// 
 + 
 +  * //If applied, this commit will// **Correct clef encoding in measure 1** ✓ 
 +  * //If applied, this commit will// **Corrected clef encoding in measure 1** ✗ 
 + 
 +This matches the style Git itself uses for auto-generated messages (for example from ''git merge'' or ''git revert''), which keeps the project history consistent.
  
 Bad examples: Bad examples:
  • en/git.txt
  • Zuletzt geändert: 2026/04/03 09:40
  • von piasteuck