GeezerVison is showing github.com — test: revise pull request guide text about code · nodejs/node@305d4de
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/pull-requests.md +6-6Lines changed: 6 additions & 6 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -107,13 +107,13 @@ git checkout -b my-branch -t upstream/HEAD |
107 | 107 |
|
108 | 108 | ### Step 3: Code |
109 | 109 |
|
110 | | -The vast majority of pull requests opened against the `nodejs/node` |
111 | | -repository includes changes to one or more of the following: |
| 110 | +Pull requests in Node.js typically involve changes to |
| 111 | +one or more of a few places in the repository. |
112 | 112 |
|
113 | | -* the C/C++ code contained in the `src` directory |
114 | | -* the JavaScript code contained in the `lib` directory |
115 | | -* the documentation in `doc/api` |
116 | | -* tests within the `test` directory. |
| 113 | +* C/C++ code contained in the `src` directory |
| 114 | +* JavaScript code contained in the `lib` directory |
| 115 | +* Documentation in `doc/api` |
| 116 | +* Tests within the `test` directory |
117 | 117 |
|
118 | 118 | If you are modifying code, please be sure to run `make lint` (or |
119 | 119 | `vcbuild.bat lint` on Windows) to ensure that the changes follow the Node.js |
|