From 394b64319de11b1010b8acfe160de13a6f3851cd Mon Sep 17 00:00:00 2001 From: mcraa <6892971+mcraa@users.noreply.github.com> Date: Tue, 21 Feb 2023 12:58:13 +0100 Subject: [PATCH] patch: updated commit message guide --- docs/COMMIT-GUIDELINES.md | 179 +++----------------------------------- 1 file changed, 10 insertions(+), 169 deletions(-) diff --git a/docs/COMMIT-GUIDELINES.md b/docs/COMMIT-GUIDELINES.md index f644452c..203e0183 100644 --- a/docs/COMMIT-GUIDELINES.md +++ b/docs/COMMIT-GUIDELINES.md @@ -12,67 +12,29 @@ over the commit history. - Be able to automatically reference relevant changes from a dependency upgrade. -The guidelines are inspired by the [AngularJS git commit -guidelines][angular-commit-guidelines]. Commit structure ---------------- -Each commit message consists of a header, a body and a footer. The header has a -special format that includes a type, a scope and a subject. +Each commit message needs to specify the semver-type. Which can be `patch|minor|major`. +See the [Semantic Versioning][semver] specification for a more detailed explanation of the meaning of these types. +See balena commit guidelines for more info about the whole commit structure. ``` -(): +: +``` +or +``` + - +
-