r3pek/log4j-affected-db
1
0
Fork 0
mirror of https://github.com/cisagov/log4j-affected-db.git synced 2024-11-22 16:40:48 +00:00
Code Releases Activity

Update PULL-EXAMPLE.md

Browse source 
Changes made as suggested by @chelsgr
This commit is contained in:
iainDe 2022-01-06 05:17:09 -06:00 committed by GitHub
parent c7f02fe859
commit 9490f075c9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
PULL-EXAMPLE.md
View file

@ -5,7 +5,7 @@ Thank you for contributing to CISA's Log4j-affected-db GitHub Repository! Please
**Step 2:** Click the file edit button.
**Step 3:** Add the blank template to the **.yml** file for new entries and fill it out with the correct data. Note: we are tracking multiple CVEs on the backend but are currently only displaying all the CVE-2021-44228. The multiple CVEs will not be listed in the table per the current request, instead the logic will determine and present a single status based on the available data in the template.
**Step 3:** Add the blank template to the **.yml** file for new entries and fill it out with the correct data.
Blank template:
```
@ -37,7 +37,6 @@ Blank template:
notes: ''
references:
- ''
reporter: cisagov
last_updated: ''
```
**Step 3:** Verify the new entry was entered before and/or after the prior and next entries.
@ -83,7 +82,6 @@ Entry example:
unauthenticated user input to the log4j component.
references:
- ''
reporter: cisagov
last_updated: '2021-12-14T00:00:00'
```
**Step 5:** Validate that your data follows the appropriate format and proceed with submitting the pull request.