8000 docs(CONTRIBUTING): how to write a breaking change · angular/angular.js@d38f6ff · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit d38f6ff

Browse files
stevemaopetebacondarwin
authored andcommitted
docs(CONTRIBUTING): how to write a breaking change
Closes #12032
1 parent 8f6dac9 commit d38f6ff

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -238,6 +238,7 @@ The body should include the motivation for the change and contrast this with pre
238238
The footer should contain any information about **Breaking Changes** and is also the place to
239239
reference GitHub issues that this commit **Closes**.
240240
241+
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
241242
242243
A detailed explanation can be found in this [document][commit-message-format].
243244

0 commit comments

Comments
 (0)
0