-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: fix small typo in 15.11.0 release #37590
Conversation
did my best with the commit message naming, if |
4a47a68
to
121051a
Compare
removed the change in the auto-generated bit and to just update the Notable Changes bit, per advice from @MylesBorins. |
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
Will update that today 👍🏻 |
121051a
to
e6786e5
Compare
Force pushed over the previous commit to use the |
The failed macOS build is unrelated to the contents of this PR 😬 |
PR-URL: #37590 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in ed633f2 |
PR-URL: #37590 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Noticed a small typo in the changelog for the release today while writing a tweet for it, wanted to help fix it. Since this typo is directly committed and is in the commit message, I'm not sure if this can/should land but figured I'd throw it up on the possibility that folks think it should land.