Skip to content

Commit 7a79441

Browse files
Trottruyadorno
authored andcommitted
doc: remove resolving-a-bug-report from contributing docs
This section isn't particularly useful in this context and contributes to making the document longer and less effective. This is part of a larger effort to make the contributing docs brief, informative, and friendly. Refs: nodejs/TSC#864 (comment) PR-URL: #36905 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de>
1 parent 707b973 commit 7a79441

File tree

2 files changed

+0
-10
lines changed

2 files changed

+0
-10
lines changed

CONTRIBUTING.md

-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,6 @@ See [details on our policy on Code of Conduct](./doc/guides/contributing/code-of
1919
* [Discussing non-technical topics](./doc/guides/contributing/issues.md#discussing-non-technical-topics)
2020
* [Submitting a Bug Report](./doc/guides/contributing/issues.md#submitting-a-bug-report)
2121
* [Triaging a Bug Report](./doc/guides/contributing/issues.md#triaging-a-bug-report)
22-
* [Resolving a Bug Report](./doc/guides/contributing/issues.md#resolving-a-bug-report)
2322

2423
## [Pull Requests](./doc/guides/contributing/pull-requests.md)
2524

doc/guides/contributing/issues.md

-9
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@
44
* [Discussing non-technical topics](#discussing-non-technical-topics)
55
* [Submitting a Bug Report](#submitting-a-bug-report)
66
* [Triaging a Bug Report](#triaging-a-bug-report)
7-
* [Resolving a Bug Report](#resolving-a-bug-report)
87

98
## Asking for General Help
109

@@ -88,13 +87,5 @@ activities, such as applying labels and closing/reopening/assigning issues.
8887
For more information on the roles and permissions, see ["Permission levels for
8988
repositories owned by an organization"](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization).
9089

91-
## Resolving a Bug Report
92-
93-
In the vast majority of cases, issues are resolved by opening a Pull Request.
94-
The process for opening and reviewing a Pull Request is similar to that of
95-
opening and triaging issues, but carries with it a necessary review and approval
96-
workflow that ensures that the proposed changes meet the minimal quality and
97-
functional guidelines of the Node.js project.
98-
9990
[Node.js help repository]: https://github.com/nodejs/help/issues
10091
[Technical Steering Committee (TSC) repository]: https://github.com/nodejs/TSC/issues

0 commit comments

Comments
 (0)