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
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions 5 CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ When the body is required it must be at least 20 characters long.

The `footer` is optional.

Any line of the commit message cannot be longer than 100 characters.
Any line of the commit message cannot be longer than 120 characters.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, we want each line to have max. 100 chars. The current limit of 120 is supposed to be a "temporary" work-around that we seem we to have forgotten to revert: bf57df3

Maybe you could try reverting that to 100 and see if CI is indeed happy.



#### <a href="commit-header"></a>Commit Message Header
Expand Down Expand Up @@ -302,12 +302,13 @@ You can include a comparison of the previous behavior with the new behavior in o
The footer can contain information about breaking changes and is also the place to reference GitHub issues, Jira tickets, and other PRs that this commit closes or is related to.

```
Fixes #<issue number>

BREAKING CHANGE: <breaking change summary>
<BLANK LINE>
<breaking change description + migration instructions>
<BLANK LINE>
<BLANK LINE>
Fixes #<issue number>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right that we used to require the issue/PR references to be above the breaking change notice, but this has changed recently. So, putting the Fixes ... section below the BREAKING CHANGE section here was intentional. See the discussion in #37951 (comment).

```

Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.