Update PULL-EXAMPLE.MD

pull/425/head
iainDe 2 years ago committed by GitHub
parent fb0a644f0b
commit 98b1ec0758
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 7
      PULL-EXAMPLE.MD

@ -40,8 +40,9 @@ Blank template:
last_updated: '' last_updated: ''
``` ```
**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 end of the file, ensure the entry ends before the file is closed out with: “...” - 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: “...”
**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.
@ -50,7 +51,7 @@ Note: not all fields have to be updated.
Entry example: Entry example:
``` ```
- vendor: CISA - vendor: CISA
product: Chirp product: Product
cves: cves:
cve-2021-4104: cve-2021-4104:
investigated: false investigated: false

Loading…
Cancel
Save