@@ -477,9 +477,8 @@ tests. This makes it much easier when bisecting to find a breaking change.
477
477
### Using ` git-node `
478
478
479
479
In most cases, using [ the ` git-node ` command] [ git-node ] of [ ` node-core-utils ` ] [ ]
480
- should be enough to help you land a Pull Request. If you discover a problem when
481
- using this tool, please file an issue
482
- [ to the issue tracker] [ node-core-utils-issues ] .
480
+ should be enough to land a pull request. If you discover a problem when using
481
+ this tool, please file an issue [ to the issue tracker] [ node-core-utils-issues ] .
483
482
484
483
Quick example:
485
484
@@ -488,12 +487,11 @@ $ npm install -g node-core-utils
488
487
$ git node land $PRID
489
488
```
490
489
491
- If it's the first time you have used ` node-core-utils ` , you will be prompted
492
- to type the password of your GitHub account and the two-factor authentication
493
- code in the console so the tool can create the GitHub access token for you.
494
- If you do not want to do that, follow
495
- [ the ` node-core-utils ` guide] [ node-core-utils-credentials ]
496
- to set up your credentials manually.
490
+ To use ` node-core-utils ` , you will need a GitHub access token. If you do not
491
+ have one, ` node-core-utils ` will create one for you the first time you use it.
492
+ To do this, it will ask for your GitHub password and two-factor authentication
493
+ code. If you wish to create the token yourself in advance, see
494
+ [ the ` node-core-utils ` guide] [ node-core-utils-credentials ] .
497
495
498
496
### Technical HOWTO
499
497
0 commit comments