-
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
fix changelog date typo (v6.17.0) #26831
Conversation
Well actually since the ideal time to figure out the prefix is before making the commit, wouldn't just looking at the modified paths with |
Node.js Collaborators, please, add 👍 here if you approve fast-tracking. |
Landed in 0622ce6 |
PR-URL: #26831 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Thanks @vsemozhetbyt and everyone. Would be interested to understand what the changelog advice about identifying subsystems for commit messages is getting at if someone has a chance to comment. |
@jmm If nobody answers here, please, create an issue with the question) |
Same typo is also at the top of https://nodejs.org/en/blog/vulnerability/february-2019-security-releases/.
On a side note, I must be misunderstanding something because I'm not seeing how the contributing advice for identifying subsystems touched when writing a commit message would help:
That output doesn't seem to help identify changed files / it's actually saying to list changed files as input to the command. I feel like the intention here would be to do something more like?:
But even so not sure how helpful that is in identifying the expected prefix. E.g. the examples given are
src
, which I assume refers to the top-levelsrc/
directory, andnet
, which I assume refers tolib/net.js
.