Skip to content

This is a very opiniated guideline used in my team. Parts of it are based on other guidelines. Some parts are based on my experience what I find useful.

License

Notifications You must be signed in to change notification settings

w666/git-guidelines

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 

Repository files navigation

git-guidelines

Commit Messages

  • Add issue number followed by colon :
    • For GitHub and GitLab issue numbers use square brackets [#123]:
    • For Jira issues brackets are not needed PROJ-123:
  • Use the imperative, present tense: "Change" not "Changed" nor "Changes"
  • Do capitalize the first letter
  • Do not end the first line with a period .

Branch Names

Branch names must all lowercase and follow the pattern

${BRANCH_TYPE}-${ISSUE_NUMBER}-${SHORT_DESCRIPTION}

for example fix-123-handle-null-pointer

Branch Types

  • feature or feat: when contains new feature or code refactoring
  • documentation or doc: any documentation chages
  • test: when adding tests
  • fix: for bug fixes

Commands

TODO

About

This is a very opiniated guideline used in my team. Parts of it are based on other guidelines. Some parts are based on my experience what I find useful.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published