User Tools

Site Tools


dev:git

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
dev:git [2024/07/08 17:08] – Adding clarification for bug numbers in commit messages. klussierdev:git [2025/04/15 13:22] (current) – Include a section on commit template under Commit Guidelines stompro
Line 40: Line 40:
   git config user.email user@hostname   git config user.email user@hostname
   git config user.name "Firstname Lastname"   git config user.name "Firstname Lastname"
 +  
 +  #Enable the Evergreen default commit template
 +  git config commit.template commit-template
      
   git checkout -b working_branch origin/main   git checkout -b working_branch origin/main
Line 66: Line 69:
 ====== Guidelines for contributors ====== ====== Guidelines for contributors ======
  
 +===== Commit Template =====
 +
 +The Evergreen git repo includes an optional commit template that can be used to help follow standard project formatting.  [[https://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=commit-template;hb=HEAD|View the current main version of the template.]]
 +
 +Enable commit template:
 +  git config commit.template commit-template
 +Disable commit template:
 +  git config --unset commit.template
 +  
 ===== Commit messages ===== ===== Commit messages =====
  
-A commit message should consist of a subject line (i.e., the first line of the commit message), then a blank line, then an optional description of the patch, followed by one or more signoffs.  The subject line should be brief, ideally no more than 60-70 characters. Although it is acceptable to omit the Launchpad bug number from commit messages while work is in progress, by pullrequest time, it should include this number if relevant.  Here is an example of a minimum commit message:+A commit message should consist of a subject line (i.e., the first line of the commit message), then a blank line, then an optional description of the patch, followed by one or more signoffs.  The subject line should be brief, ideally no more than 60-70 characters. Although it is acceptable to omit the Launchpad bug number from commit messages while work is in progress, by pullrequest time, each commit in a branch should include this number if relevant.  Here is an example of a minimum commit message:
  
   LP#24544: fix the quuxifier   LP#24544: fix the quuxifier
dev/git.1720472905.txt.gz · Last modified: 2024/07/08 17:08 by klussier

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.