Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add git node security --cleanup #54381

Merged
merged 1 commit into from
Aug 17, 2024

Conversation

RafaelGSS
Copy link
Member

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Aug 14, 2024
Comment on lines +162 to +164
* [ ] `git node security --cleanup`. This command will:
* Close PRs and backports.
* Close HackerOne reports:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optional nit that I think simplifies layout without sacrificing clarity. (But it's a nit, so disregard if you disagree!)

Suggested change
* [ ] `git node security --cleanup`. This command will:
* Close PRs and backports.
* Close HackerOne reports:
* [ ] `git node security --cleanup`. This command will close PRs and backports.
It will also close HackerOne reports:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, the document is following the approach of:

  • automated command (git node security --something)
  • operation 1 that is automated
  • operation 2 that is automated
  • manual work

So, in case of the automated command fails (as it's still experimental), users need to know which steps to follow exactly.

Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with or without my nit.

@RafaelGSS RafaelGSS added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels Aug 17, 2024
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 17, 2024
@nodejs-github-bot nodejs-github-bot merged commit 9e83853 into nodejs:main Aug 17, 2024
23 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 9e83853

RafaelGSS added a commit that referenced this pull request Aug 19, 2024
PR-URL: #54381
Reviewed-By: Ruy Adorno <ruy@vlt.sh>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
@RafaelGSS RafaelGSS mentioned this pull request Aug 19, 2024
RafaelGSS added a commit that referenced this pull request Aug 21, 2024
PR-URL: #54381
Reviewed-By: Ruy Adorno <ruy@vlt.sh>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants