GeezerVison is showing github.com — doc: remove unnecessary contributing.md section · nodejs/node@fa82cbc
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: CONTRIBUTING.md -1Lines changed: 0 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -15,7 +15,6 @@ See [details on our policy on Code of Conduct](./doc/guides/contributing/code-of |
15 | 15 |
|
16 | 16 | ## [Issues](./doc/guides/contributing/issues.md) |
17 | 17 |
|
18 | | -* [How to Contribute in Issues](./doc/guides/contributing/issues.md#how-to-contribute-in-issues) |
19 | 18 | * [Asking for General Help](./doc/guides/contributing/issues.md#asking-for-general-help) |
20 | 19 | * [Discussing non-technical topics](./doc/guides/contributing/issues.md#discussing-non-technical-topics) |
21 | 20 | * [Submitting a Bug Report](./doc/guides/contributing/issues.md#submitting-a-bug-report) |
|
Collapse file
Copy file name to clipboardExpand all lines: doc/guides/contributing/issues.md -17Lines changed: 0 additions & 17 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
|
1 | 1 | # Issues |
2 | 2 |
|
3 | | -* [How to Contribute in Issues](#how-to-contribute-in-issues) |
4 | 3 | * [Asking for General Help](#asking-for-general-help) |
5 | 4 | * [Discussing non-technical topics](#discussing-non-technical-topics) |
6 | 5 | * [Submitting a Bug Report](#submitting-a-bug-report) |
7 | 6 | * [Triaging a Bug Report](#triaging-a-bug-report) |
8 | 7 | * [Resolving a Bug Report](#resolving-a-bug-report) |
9 | 8 |
|
10 | | -## How to Contribute in Issues |
11 | | - |
12 | | -For any issue, there are fundamentally three ways an individual can |
13 | | -contribute: |
14 | | - |
15 | | -1. By opening the issue for discussion: For instance, if you believe that you |
16 | | - have uncovered a bug in Node.js, creating a new issue in the `nodejs/node` |
17 | | - issue tracker is the way to report it. |
18 | | -2. By helping to triage the issue: This can be done either by providing |
19 | | - supporting details (a test case that demonstrates a bug), or providing |
20 | | - suggestions on how to address the issue. |
21 | | -3. By helping to resolve the issue: Typically this is done either in the form |
22 | | - of demonstrating that the issue reported is not a problem after all, or more |
23 | | - often, by opening a Pull Request that changes some bit of something in |
24 | | - `nodejs/node` in a concrete and reviewable manner. |
25 | | - |
26 | 9 | ## Asking for General Help |
27 | 10 |
|
28 | 11 | Because the level of activity in the `nodejs/node` repository is so high, |
|