[PR #63] [CLOSED] FEAT: prescribe ALL-CAPS type when commit includes breaking change #272

New Issue

GiteaMirror · 2026-02-17T11:56:54-06:00

GiteaMirror commented

2026-02-17 11:56:54 -06:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/63
Author: @apetro
Created: 7/5/2018
Status: ❌ Closed

Base: master ← Head: emphasize-breaking-changes

📝 Commits (1)

3e8a547 FEAT: prescribe ALL-CAPS type when commit includes breaking change

📊 Changes

1 file changed (+4 additions, -2 deletions)

View changed files

📝 index.md (+4 -2)

📄 Description

BREAKING CHANGE: requires type in ALL-CAPS when the commit includes a breaking change, whereas previously type would always be lowercase. Tools enforcing Conventional Commits as understood prior to this change may flag or fail to correctly parse commit messages indicating breaking changes under this version of the spec.

When a commit includes a breaking change, surely this is the most important thing to say about that commit. So lead with it. Indicating the breaking-change-ness of a commit it its header rather than just in its body and footer makes it easier to skim to, notice, and parse out (from abbreviated representations of the commit log) these changes.

This is another way of getting at the indicate-breaking-changes-in-the-header problem that #43 is trying to solve with a sigil. It might be that the sigil solution is better. I'm not sure that ALL-CAPS-ing the type: is the move to make here.

I do think something should be done to indicate the breakingness of changes in the header rather than only in the body or footer.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/conventional-commits/conventionalcommits.org/pull/63 **Author:** [@apetro](https://github.com/apetro) **Created:** 7/5/2018 **Status:** ❌ Closed **Base:** `master` ← **Head:** `emphasize-breaking-changes` --- ### 📝 Commits (1) - [`3e8a547`](https://github.com/conventional-commits/conventionalcommits.org/commit/3e8a5478e9064458e1cc655affedf28db75f5320) FEAT: prescribe ALL-CAPS type when commit includes breaking change ### 📊 Changes **1 file changed** (+4 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `index.md` (+4 -2) </details> ### 📄 Description BREAKING CHANGE: requires type in ALL-CAPS when the commit includes a breaking change, whereas previously type would always be lowercase. Tools enforcing Conventional Commits as understood prior to this change may flag or fail to correctly parse commit messages indicating breaking changes under this version of the spec. When a commit includes a breaking change, surely this is the most important thing to say about that commit. So lead with it. Indicating the breaking-change-ness of a commit it its header rather than just in its body and footer makes it easier to skim to, notice, and parse out (from abbreviated representations of the commit log) these changes. ----- This is another way of getting at the indicate-breaking-changes-in-the-header problem that #43 is trying to solve with a sigil. It might be that the sigil solution is better. I'm not sure that ALL-CAPS-ing the _type:_ is the move to make here. I do think *something* should be done to indicate the breakingness of changes in the header rather than only in the body or footer. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-02-17 11:56:54 -06:00

GiteaMirror closed this issue

2026-02-17 11:56:54 -06:00

GiteaMirror referenced this issue

2026-02-17 12:02:19 -06:00

[PR #272] [MERGED] docs: fix "ommitted" typo #406

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#272