-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
doc: include updating release optional step #46089
doc: include updating release optional step #46089
Conversation
Review requested:
|
833a9c4
to
09c68ee
Compare
doc/contributing/releases.md
Outdated
conditions: | ||
|
||
* Unstable CI | ||
* Bad commit, requiring a git bisect and updating the proposal |
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.
I think it'd be useful to have the Git steps documented in this section for when we need to remove or adjust commits in the release. As a draft suggestion, I think including steps like this would be useful:
Remove or adjust problematic commit(s):
# update staging
git checkout staging
git rebase -i ... # rebase to drop or edit the bad commit(s)
git push -f upstream staging
# rebase proposal against the updated staging branch
git checkout proposal
git rebase upstream/staging
Reminder to re-run changelog-maker
and update the changelog to include the new/changed Git SHAs. (Easily forgotten).
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.
Just updated
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.
Actually, it's missing a fix. In case of dropping a commit, we need to reset the branch instead of rebasing
git reset --hard upstream/staging
I'll adjust it.
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.
Done!
09c68ee
to
eebd1b8
Compare
eebd1b8
to
785f79d
Compare
Landed in fd71d1a |
PR-URL: nodejs#46089 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Ruy Adorno <ruyadorno@google.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
PR-URL: #46089 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Ruy Adorno <ruyadorno@google.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
PR-URL: #46089 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Ruy Adorno <ruyadorno@google.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
PR-URL: #46089 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Ruy Adorno <ruyadorno@google.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
cc @nodejs/releasers