Skip to content

docs(code-security): fix advisory disclosure punctuation #46051

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.

Sign up for GitHub

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

Closed
aniruddhaadak80 wants to merge 1 commit into from
+1 −1
Closed

docs(code-security): fix advisory disclosure punctuation #46051

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ncepts/vulnerability-reporting-and-management/repository-security-advisories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,6 @@ Whenever possible, you should **add a fix version to a security advisory prior t

Depending on the vulnerability, you may need to adjust your approach. If a fix version is:

* **Imminently available**, and you are able to, wait to disclose the issue when the fix is ready.
* **Imminently available**, and you are able to wait to disclose the issue when the fix is ready.
* **In development but not yet available**, mention this in the advisory, and edit the advisory later, after publication.
* **Not planned**, be clear about it in the advisory so that your users don't contact you to ask when a fix will be made. In this case, it is helpful to include steps users can take to mitigate the issue.
Loading