.commit-template

# ==[ Subject: One line only short meaningful description for logs ]===|


# ==[ Details: Describe what changed and explain why it changed ]======|


# Change log entry (see below for instructions).
#[ChangeLog][][]

# ==[ Footers: Uncomment and edit where applicable ]===================|
#
# One task per entry. Add a space after the colon.
# Use Fixes to automatically close an issue, Reopens to automatically
# reopen an issue, and Task-number to reference it without further
# action.
# You do not need to include Task-Number where Fixes or Reopens is
# specified for the same issue.
#Fixes: 
#Reopens: 
#Task-number: 
#Coverity-Id: 
#
# Add a space-separated list of target branches that the change should
# be cherry-picked to automatically.
#Pick-to: 
#
# ==[ Please wrap at 72 characters ]===================================|
#
# Remember to read http://wiki.qt.io/Commit_Policy
#
# Change log entry: If this commit adds a significant feature, fixes an
# issue or contains a behavior change that is relevant to others,
# add a change log entry. It can be multiple lines long and ends with an
# empty newline. Try to integrate it into the flow of the commit message
# to avoid redundancy.
# Use the module name to indicate the area of the change e.g. [QtCore].
# Optionally specify a class or subtopic [QtNetwork][QSslSocket].
# Other common tags are: [General], [Important Behavior Changes],
# [Platform Specific Changes][Windows][OS X][Linux/XCB].
#
# [ChangeLog][module][class/topic] description of the really important
# change that was just made on several lines.