1# <feature-name>: <subject>
2# |<----  Using a maximum of 50 characters  ---->|
3#
4# Explain why this change is being made
5# |<----   Try to limit each line to a maximum of 72 characters   ---->|
6
7# Ticket: <JIRA #id>
8# Type: <type>
9# Fixes: <offending-git-commit-id>
10# Change-Id: <sha1>
11# Signed-off-by: <email>
12#
13#
14# --- COMMIT END ---
15#
16# Type can be
17#    feature     (new feature)
18#    fix         (bug fix)
19#    refactor    (refactoring production code)
20#    improvement (minor improvements in existing feature)
21#    style       (formatting, missing semi colons, etc; no code change)
22#    docs        (changes to documentation)
23#    test        (adding or refactoring tests; no production code change)
24#    make        (change the build process, or tools, or infrastructure)
25#
26# feature-name: Is the name of the VPP feature, plugin or directory.
27#               Commits across multiple components should be split.
28#               E.g. ip, fib, nat, acl, host, api
29#
30# Fixes: If type is fix refers to the original commit (optional).
31# Ticket: Refers to JIRA ticket if it exists (optional).
32#
33# --------------------
34# Remember to:
35#    Lowercase the subject line.
36#    Use the imperative mood in the subject line.
37#    Not end the subject line with a period.
38#    Separate subject from body with a blank line.
39#    Use the body to explain what and why vs. how.
40#    Use multiple lines with "-" for bullet points in body.
41# --------------------
42# Usage:
43#
44# The template is automatically added to the current repository by
45# make install-dep.
46# (git config commit.template .git_commit_template.txt)
47#
48# --------------------
49