| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Nit: can we use the triple ` instead of the indentation? I think it's more common in our guides.
Sorry, something went wrong.
There was a problem hiding this comment.
```console $ git clone https://github.com/npm/npm.git ```
Would be nice
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: I would add a comment explaining that the assumption is that the node repo is in the same directory of the npm repo.
Sorry, something went wrong.
There was a problem hiding this comment.
Or just cd /path/to/node
Sorry, something went wrong.
There was a problem hiding this comment.
Remove?
Sorry, something went wrong.
Sorry, something went wrong.
|
@MylesBorins do you want to wait further? |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good! Couple of minor bits but otherwise 👍
Sorry, something went wrong.
There was a problem hiding this comment.
We don't use master. This should be latest.
Sorry, something went wrong.
There was a problem hiding this comment.
Shouldn't this be -A, to make sure files are both added and removed?
Sorry, something went wrong.
There was a problem hiding this comment.
When I was doing it with -A it wasn't adding all the files. I believe add -f will add and remove.
Sorry, something went wrong.
There was a problem hiding this comment.
As of git 2.0, git add adds removed files as well as added files.
git add -f is about adding gitignored files, not sure we'd want that. @MylesBorins which files weren't being added?
Sorry, something went wrong.
There was a problem hiding this comment.
Yeah, if some files are missing, we should probably modify a rule in our .gitignore
Sorry, something went wrong.
There was a problem hiding this comment.
I've updated and opened #17363
Sorry, something went wrong.
There was a problem hiding this comment.
It might be worth warning folks that this might end up including changes to -other- licenses, and that wouldn't be appropriate for this commit. They should make sure to check that any changes are actually npm-check related.
Sorry, something went wrong.
There was a problem hiding this comment.
I would add a note to run npm dist-tag ls npm and make sure this is the latest dist-tag. latest on git is usually released as next when it's time to downstream.
Sorry, something went wrong.
There was a problem hiding this comment.
fixed below
Sorry, something went wrong.
There was a problem hiding this comment.
sp: necessary
Sorry, something went wrong.
|
Updated with requested changes. PTAL |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM apart from the git add -f thing, which I'm not sure about.
Sorry, something went wrong.
There was a problem hiding this comment.
Maybe just
git remote update -p
git checkout -b npm-x.y.z origin/master
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, something went wrong.
|
We explicitly want to add all files in the npm folder including those
normally ignored
This is similar to eslint / remark deps
…On Nov 26, 2017 7:54 PM, "Michaël Zasso" ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In doc/guides/maintaining-npm.md
<#16541 (comment)>:
> +
+```console
+$ cd /path/to/node
+$ git checkout master
+$ git remote update -p
+$ git reset --hard origin master
+$ git checkout -b npm-x.y.z
+$ cd deps
+$ rm -rf npm
+```
+
+## Step 4: Extract and commit new npm
+
+```console
+$ tar zxf /path/to/npm/release/npm-x.y.z.tgz
+$ git add -f npm
Yeah, if some files are missing, we should probably modify a rule in our
.gitignore
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16541 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV4GcrG-qDwxVOmonfmx0OCgZlP5Mks5s6UN9gaJpZM4QIgKS>
.
|
Sorry, something went wrong.
|
I've opened #17363 to help with the problem of files in the npm tree not being tracked by default |
Sorry, something went wrong.
|
I think an npm update has gotten into the branch... |
Sorry, something went wrong.
|
lol. This is what I get for trying to test things and multi tasking. I'll update when I get back to computer |
Sorry, something went wrong.
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs
|
@gibfahn ptal. This should be in working order now, I'll land in 24 hours if no one has any complaints. As this primarily mirrors the guide found on the npm wiki I don't think we need to block on the gitignore PR to land this |
Sorry, something went wrong.
|
@MylesBorins went ahead and pushed my suggestion, remove it if you disagree (I'm assuming it simply got lost). LGTM. This has 11 (!) approvals, and you've addressed all of @zkat's suggestions, so this should be good to land. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
👍
Sorry, something went wrong.
Sorry, something went wrong.
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
This is based on the guide found on their wiki refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs PR-URL: #16541 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
| Back | FazBrowse Home | New Git URL |
This is based on the guide found on their wiki
refs: https://github.com/npm/npm/wiki/CLI-Team-Process#submitting-the-new-latest-x-to-nodejs
/cc @nodejs/npm