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

Update PULL-EXAMPLE.md

Browse source 
Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
This commit is contained in:
Chris Sullivan 2022-01-06 13:43:53 -05:00 committed by GitHub
parent 1140f68912
commit 7ca08081f8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
PULL-EXAMPLE.md
View file

@ -41,8 +41,8 @@ Blank template:
``` ```
**Step 3:** Verify the new entry was entered before and/or after the prior and next entries. **Step 3:** Verify the new entry was entered before and/or after the prior and next entries.
- If you are adding it to the beginning of the file, ensure you are pasting it after “software:” and before the next entry starting with “- vendor:”. - If you are adding it to the beginning of the file, ensure you are pasting it after `software:` and before the next entry starting with `- vendor:`.
- If you are adding it to the end of the file, ensure the entry ends before the file is closed out with: “...” - If you are adding it to the end of the file, ensure the entry ends before the file is closed out with `...`.
**Step 4:** When you add content to the file, remove the '' or [] for fields which are replaced with values (strings '' or lists [] should be replaced as shown in the example below, with list values on the following line(s), starting with hyphen(s) “-”). The symbols should only remain used when fields remain empty. For example, fixed_versions: [] in our example below remains as is, given there are no patched versions available for this entry. **Step 4:** When you add content to the file, remove the '' or [] for fields which are replaced with values (strings '' or lists [] should be replaced as shown in the example below, with list values on the following line(s), starting with hyphen(s) “-”). The symbols should only remain used when fields remain empty. For example, fixed_versions: [] in our example below remains as is, given there are no patched versions available for this entry.