... | ... | @@ -4,7 +4,7 @@ In addition to requiring a sign off message for open source projects we make use |
|
|
|
|
|
NOTE: Format guidelines for conventional commits are only enforced for commit messages to a protected branch or on a MR to a protected branch. But we recommend doing your best to maintain this format at all times. Please try to be short and informative in the description. This will help other to easier understand the commit. The description should be max. 50 characters.
|
|
|
|
|
|
TIP: split your commits up into logical chunks. everything regarding one topic into one commit. In case you made many significant changes do not put them into one single commit. splitting them up into individual commits will make review and merging easier.
|
|
|
TIP: Commit often! Do not put multiple changes across sections into one commit. Splitting them up into individual commits will make review and merging easier.
|
|
|
|
|
|
The commit message should be structured as follows
|
|
|
|
... | ... | |