From 1df2e03e6c7dbf7cd47aee956f058949b7a84635 Mon Sep 17 00:00:00 2001 From: "dennis.ludwig" Date: Fri, 2 Jul 2021 09:54:40 +0200 Subject: [PATCH] conventionalcommits.md was not featured by mistake --- radar/2021-01-01/conventionalcommits.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/radar/2021-01-01/conventionalcommits.md b/radar/2021-01-01/conventionalcommits.md index e7c2e4c..5b25c82 100644 --- a/radar/2021-01-01/conventionalcommits.md +++ b/radar/2021-01-01/conventionalcommits.md @@ -2,7 +2,7 @@ title: "Conventional Commits" ring: trial quadrant: methods-and-patterns -featured: false + --- The Conventional Commits specification is a lightweight convention on top of commit messages. It provides a small set of rules for writing commit messages and therefore creating an explicit commit history. The convention dovetails with [SemVer](/methods-and-patterns/semver2.html), by describing the features, fixes, and breaking changes made in commit messages. The specification contains only 16 items that are easy to follow. The predefined structure allows everyone in the team to get a better overview of what the commit messages relates to and what part of the code a change has to do with. Some benefits of using these specifications include: the ability to automatically generate changelogs, the ability to determine a semantic version bump (based on the types of commits landed) and being able to communicate the nature of changes to teammates and stakeholders.