@@ -419,9 +419,8 @@ tests. This makes it much easier when bisecting to find a breaking change.
419
419
### Using ` git-node `
420
420
421
421
In most cases, using [ the ` git-node ` command] [ git-node ] of [ ` node-core-utils ` ] [ ]
422
- should be enough to help you land a Pull Request. If you discover a problem when
423
- using this tool, please file an issue
424
- [ to the issue tracker] [ node-core-utils-issues ] .
422
+ should be enough to land a pull request. If you discover a problem when using
423
+ this tool, please file an issue [ to the issue tracker] [ node-core-utils-issues ] .
425
424
426
425
Quick example:
427
426
@@ -430,12 +429,11 @@ $ npm install -g node-core-utils
430
429
$ git node land $PRID
431
430
```
432
431
433
- If it's the first time you have used ` node-core-utils ` , you will be prompted
434
- to type the password of your GitHub account and the two-factor authentication
435
- code in the console so the tool can create the GitHub access token for you.
436
- If you do not want to do that, follow
437
- [ the ` node-core-utils ` guide] [ node-core-utils-credentials ]
438
- to set up your credentials manually.
432
+ To use ` node-core-utils ` , you will need a GitHub access token. If you do not
433
+ have one, ` node-core-utils ` will create one for you the first time you use it.
434
+ To do this, it will ask for your GitHub password and two-factor authentication
435
+ code. If you wish to create the token yourself in advance, see
436
+ [ the ` node-core-utils ` guide] [ node-core-utils-credentials ] .
439
437
440
438
### Technical HOWTO
441
439
0 commit comments