@@ -101,16 +101,17 @@ describing a security issue, take the following steps:
101
101
[ SECURITY.md] [ security reporting ] .
102
102
* Move the issue to the private repo called
103
103
[ premature-disclosures] ( https://github.com./nodejs/premature-disclosures ) .
104
- * For any related pull requests create an associated issue in the
105
- ` premature-disclosures ` repo and add a copy of the patch for the
106
- pull request, and screenshots of discussion on the PR to the issue.
107
- * Open a ticket with GitHub asking that the PRs be deleted through
104
+ * For any related pull requests, create an associated issue in the
105
+ ` premature-disclosures ` repository. Add a copy of the patch for the
106
+ pull request to the issue. Add screenshots of discussion from the pull request
107
+ to the issue.
108
+ * Open a ticket with GitHub asking that the pull requests be deleted through
108
109
[ GitHub suppport] ( https://support.github.com./contact )
109
110
using Node.js(team) as the account organization.
110
111
* Open a new issue in the repository in which the issue was originally
111
- reported with a brief FYI to the originator. ` FYI @xxxx we asked github
112
- to delete your PR while we work on releases in private.` with the title
113
- ` FYI - PR deleted #YYYY ` .
112
+ reported with a brief FYI to the originator: " FYI @xxxx we asked GitHub
113
+ to delete your pull request while we work on releases in private." with the
114
+ title ` FYI - pull request deleted #YYYY ` .
114
115
* Email
` [email protected] ` with the link to the issues in the
115
116
` premature-disclosures ` repo so that the TSC is aware that they
116
117
may need to expedite handling of the issue due to premature
0 commit comments