Skip to content
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

When generating a stacked changelog, note which branch/es contain a commit #14728

Merged
merged 2 commits into from
Jan 25, 2023

Conversation

DHowett
Copy link
Member

@DHowett DHowett commented Jan 24, 2023

New-TerminalStackedChangelog used to generate logs that looked like this:

* [3] A commit that was seen 3 times
* A commit that was only seen once
* [2] Some other commit

Now it will generate logs that look like this:

   / base..branch-1
   |/ base..branch-2
   ||/ base..branch-3
* [XXX] A commit that was seen 3 times
* [ X ] A commit that was only seen once
* [XX ] Some other commit

This format is more expressive, as it indicates which branches contain which commits.

As a reminder, my release note writing style starts with a stacked changelog. It's how I tell (1) which commits are in the new preview release only, (2) which commits are in the new preview and the new stable release and (3) which commits were already released in a previous stable release.

Changes from 1 get included in the new changelog, changes from 2 get included in both and changes from 3 get deleted because they have already been released.

…ommit

New-TerminalStackedChangelog used to generate logs that looked like
this:

```
* [3] A commit that was seen 3 times
* A commit that was only seen once
* [2] Some other commit
```

Now it will generate logs that look like this:

```
   / base..branch-1
   |/ base..branch-2
   ||/ base..branch-3
* [XXX] A commit that was seen 3 times
* [ X ] A commit that was only seen once
* [XX ] Some other commit
```

This format is more expressive, as it indicates _which branches_ contain
which commits.

As a reminder, my release note writing style starts with a stacked
changelog. It's how I tell (1) which commits are in the new preview
release only, (2) which commits are in the new preview and the new
stable release and (3) which commits were already released in a previous
stable release.

Changes from 1 get included in the new changelog, changes from 2 get
included in both and changes from 3 get deleted because they have
already been released.
@carlos-zamora carlos-zamora merged commit 6a61033 into main Jan 25, 2023
@carlos-zamora carlos-zamora deleted the dev/duhowett/stacked-changelog branch January 25, 2023 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants