-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathgitmessage
More file actions
39 lines (37 loc) · 1.05 KB
/
gitmessage
File metadata and controls
39 lines (37 loc) · 1.05 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
# Title: Summary, imperative, start upper case, include JIRA ID
# No more than 50 chars. #### 50 chars is here: #
#
# Remember blank line between title and body.
#
# Body: Explain *why* and *what* (not *how*)
# Wrap at 72 chars. ################################## which is here: #
#
# example commit message:
#
# JIRA-1234: Add new feature
#
# Why:
#
# Customers need new feature.
#
# This commit:
#
# Introduces the new feature.
#
# At the end: Include Co-authored-by for all contributors.
# Include at least one empty line before it. Format:
# Co-authored-by: name <user@users.noreply.github.com>
#
# How to Write a Git Commit Message:
# https://chris.beams.io/posts/git-commit/
#
# 1. Separate subject from body with a blank line
# 2. Limit the subject line to 50 characters
# 3. Capitalize the subject line
# 4. Do not end the subject line with a period
# 5. Use the imperative mood in the subject line
# 6. Wrap the body at 72 characters
# 7. Use the body to explain what and why vs. how
#
# Creating a code review culture:
# https://www.youtube.com/watch?v=PJjmw9TRB7s