OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-01-05 19:20:34 +01:00
Code Issues Packages Projects Releases Wiki Activity

Remove redundant usually (#1288)

Browse Source
This commit is contained in:
Yechan Bae
2022-07-31 18:37:19 -04:00
committed by GitHub
parent c1ae578c27
commit 2380d517ee
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
MAINTAINERS_GUIDE.md
View File

@@ -6,7 +6,7 @@ Reviewing a pull request, step by step:
This is something first-time submitters may struggle with.
Usually you can usually make changes directly to the sumbitter's branch. It's a great way to make CI pass and help out first-timers, but avoid making substantial changes to content this way without consuling the submitter.
You can usually make changes directly to the sumbitter's branch. It's a great way to make CI pass and help out first-timers, but avoid making substantial changes to content this way without consuling the submitter.
## Make sure the developers of the crate in question are aware of the issue
@@ -33,7 +33,7 @@ The date should be set to the original disclosure of the issue, not the date of
## Check if the advisory came from GHSA
GHSA advisory info is licensed under [CC-BY-4.0](https://docs.github.com/en/site-policy/github-terms/github-terms-for-additional-products-and-features#12-advisory-database), while most other databases (including RustSec) are in the public domain.
GHSA advisory info is licensed under [CC-BY-4.0](https://docs.github.com/en/site-policy/github-terms/github-terms-for-additional-products-and-features#12-advisory-database), while most other databases (including RustSec) are in the public domain.
If the advisory came from GHSA, we have two options: