[PR #134] [MERGED] feat: introduce ! for indicating breaking changes in header #2294

New Issue

GiteaMirror · 2026-04-16T01:22:09-05:00

GiteaMirror commented

2026-04-16 01:22:09 -05:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/134
Author: @bcoe
Created: 3/23/2019
Status: ✅ Merged
Merged: 4/10/2019
Merged by: @bcoe

Base: master ← Head: introduce-bang

📝 Commits (2)

ed6320f feat: introduce bang to spec
208e0a0 add example of !

📊 Changes

1 file changed (+9 additions, -0 deletions)

View changed files

📝 content/next/index.md (+9 -0)

📄 Description

Based on discussion in #43 I've made an effort to describe a new ! character, which can optionally be used in the header to indicate a breaking change.

The value I see in making this optional:

the feature will be available for folks who would like to use it, but the spec doesn't drift away from angular's commit message format.
tooling can more gradually move over to this new semantic construct.

I propose we wait and see how widely ! is adopted, and consider making it a MUST in the future if it's seeing wide adoption.

CC: @DominicKramer, @apetro, @ofrobots

_{🔄 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/134 **Author:** [@bcoe](https://github.com/bcoe) **Created:** 3/23/2019 **Status:** ✅ Merged **Merged:** 4/10/2019 **Merged by:** [@bcoe](https://github.com/bcoe) **Base:** `master` ← **Head:** `introduce-bang` --- ### 📝 Commits (2) - [`ed6320f`](https://github.com/conventional-commits/conventionalcommits.org/commit/ed6320f89e3cf79166c6ed790770554135a2f497) feat: introduce bang to spec - [`208e0a0`](https://github.com/conventional-commits/conventionalcommits.org/commit/208e0a07a2c41cc96f17456b38991fb8845a0ed9) add example of \! ### 📊 Changes **1 file changed** (+9 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `content/next/index.md` (+9 -0) </details> ### 📄 Description Based on discussion in #43 I've made an effort to describe a new `!` character, which can optionally be used in the header to indicate a breaking change. The value I see in making this optional: * the feature will be available for folks who would like to use it, but the spec doesn't drift away from angular's commit message format. * tooling can more gradually move over to this new semantic construct. I propose we wait and see how widely `!` is adopted, and consider making it a MUST in the future if it's seeing wide adoption. CC: @DominicKramer, @apetro, @ofrobots --- <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-04-16 01:22:09 -05:00

GiteaMirror closed this issue

2026-04-16 01:22:09 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#2294