-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update the changelog when creating an RC #10795
Conversation
|
Builds ready [e0bf1cc]
Page Load Metrics (665 ± 62 ms)
|
5ed8808
to
ddfd922
Compare
e0bf1cc
to
e7c7055
Compare
Builds ready [e7c7055]
Page Load Metrics (549 ± 43 ms)
|
e7c7055
to
79b8ed5
Compare
Builds ready [79b8ed5]
Page Load Metrics (559 ± 37 ms)
|
79b8ed5
to
0402931
Compare
Builds ready [0402931]
Page Load Metrics (571 ± 40 ms)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good except for a typo.
The changelog will now be automatically updated when a release branch is created. A new release header along with changelog entries for any new commits will be added. Note that this changelog will still need to be manually cleaned up, but it's one less manual step at least. The old Bash script for adding a new release header to the changelog has been removed, as that functionality is now built into the changelog update script. A new script has been added to commit any changes made to the manifest and changelog. This step used to happen at the end of the bump manifest version script, but now the changelog update relies upon the manifest version bump happening first, so it needed to be re-ordered. The changes should only be committed on the first run of the branch, as it's contingent upon the manifest changing (due to the version bump). Further changelog updates won't trigger new automatic commits.
0402931
to
02ad6c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I've just created the branch |
ffffuuuuuuu
|
The check for manifest changes was wrong on two counts. Firstly it was supposed to check that there *are* changes, but instead it was bailing if there were *no* changes (the opposite of what was intended). Second, it was including changelog changes as well, when it should have only considered manifest changes.
It worked! d6b5abd ... after fixing a couple more mistakes 😅 . I put each bug fix in a separate commit - check out the most recent two since your approval to see what they were. |
That status check shouldn't affect this PR thankfully, because this isn't a release branch. It was only triggered because this commit was used in a release branch. GitHub applies these status checks by commit it seems, not by branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, now it looks good!
Builds ready [c6c5daa]
Page Load Metrics (513 ± 38 ms)
|
The changelog will now be automatically updated when a release branch is created. A new release header along with changelog entries for any new commits will be added.
Note that this changelog will still need to be manually cleaned up, but it's one less manual step at least.
The old Bash script for adding a new release header to the changelog has been removed, as that functionality is now built into the changelog update script.
A new script has been added to commit any changes made to the manifest and changelog. This step used to happen at the end of the bump manifest version script, but now the changelog update relies upon the manifest version bump happening first, so it needed to be re-ordered. The changes should only be committed on the first run of the branch, as it's contingent upon the manifest changing (due to the version bump). Further changelog updates won't trigger new automatic commits.
Relates to #10752
Manual testing steps: