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

fix changelog date typo (v6.17.0) #26831

Closed
wants to merge 1 commit into from

Conversation

jmm
Copy link
Contributor

@jmm jmm commented Mar 21, 2019

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:

Check the output of git log --oneline files/you/changed to find out what subsystems your changes touch.

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?:

git log --name-only master..

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-level src/ directory, and net, which I assume refers to lib/net.js.

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Mar 21, 2019
@jmm
Copy link
Contributor Author

jmm commented Mar 21, 2019

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 git status be more to the point than anything involving git log?

@vsemozhetbyt
Copy link
Contributor

@vsemozhetbyt
Copy link
Contributor

Node.js Collaborators, please, add 👍 here if you approve fast-tracking.

@vsemozhetbyt vsemozhetbyt added fast-track PRs that do not need to wait for 48 hours to land. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Mar 21, 2019
@vsemozhetbyt
Copy link
Contributor

Landed in 0622ce6
Thank you!

vsemozhetbyt pushed a commit that referenced this pull request Mar 21, 2019
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>
@jmm
Copy link
Contributor Author

jmm commented Mar 22, 2019

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.

@vsemozhetbyt
Copy link
Contributor

@jmm If nobody answers here, please, create an issue with the question)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations. fast-track PRs that do not need to wait for 48 hours to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants