Skip to content

[skip changelog] Fix contributing instructions re: skipping changelog #916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 7, 2020
Merged

[skip changelog] Fix contributing instructions re: skipping changelog #916

merged 1 commit into from
Sep 7, 2020

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Aug 24, 2020

Please check if the PR fulfills these requirements

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows
    our contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce?

Docs update.

  • What is the current behavior?

The arduino/arduino-cli repository's automatic changelog generation system adds a changelog item for every commit, except those that start with "[skip changelog]". This is useful for keeping the changelog to only mentioning the changes that are significant to the user.

All pull requests are merged using GitHub's "Squash & Merge" feature.

The behavior of "Squash & Merge":

  • If the PR only contains a single commit, the pre-filled squash commit message is taken from the commit, not the PR.
  • If the PR contains multiple commits, the prefilled squash commit title is the PR title.

This means that a PR will end up in the changelog against the wishes of the contributor when all of the following occur:

  • The PR author followed the instructions and only added "[skip changelog]" to the PR title.
  • The PR only contains a single commit.
  • The maintainer who merges the PR uses the pre-filled commit message provided by GitHub.

The first two conditions are common. There is evidence that the third will also be common.

  • What is the new behavior?

To make the instructions as easy as possible to follow, the contributor is now instructed to add "[skip changelog]" to both the commit message and PR title, even though it is really only necessary to add it to one or the other, depending on the conditions.

  • Does this PR introduce a breaking change?

No

The arduino/arduino-cli repository's automatic changelog generation system adds a changelog item for every commit, except those that start with "[skip changelog]". This is useful for keeping the changelog to only mentioning the changes that are significant to the user.

All pull requests are merged using GitHub's "Squash & Merge" feature.

The behavior of "Squash & Merge":

- If the PR only contains a single commit, the pre-filled squash commit message is taken from the commit, not the PR.
- If the PR contains multiple commits, the prefilled squash commit title is the PR title.

This means that a PR will end up in the changelog against the wishes of the contributor when all of the following occur:

- The PR author followed the instructions and only added "[skip changelog]" to the PR title.
- The PR only contains a single commit.
- The maintainer who merges the PR uses the pre-filled commit message provided by GitHub.

The first two conditions are common. There is evidence that the third will also be common.

To make the instructions as easy as possible to follow, the contributor is now instructed to add "[skip changelog]" to both the commit message and PR title, even though it is really only necessary to add it to one or the other, depending on the conditions.
@per1234 per1234 requested a review from rsora August 24, 2020 04:35
@per1234 per1234 added the topic: documentation Related to documentation for the project label Aug 24, 2020
@per1234 per1234 merged commit 5045656 into arduino:master Sep 7, 2020
@per1234 per1234 self-assigned this Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants