> I realize this is a customer-driven diff, but if possible, since this is a
> public code base, could you provide some (redacted), public-facing testing
> instructions?
Sure! To test this change you need to:
1. Create a 'subprojects' folder in the root of ubuntu-cve-tracker and, inside this new one, another folder with the name of your subproject.
2. Populate config.yml inside the subproject as needed by `load_external_subprojects` function in cve_lib. You need to provide all the mandatory fields.
3. Run scripts/check-syntax to verify that the tool alerts about a missing CVE when cve_triage is set to true and that it doesn't if false.
> This has no impact on whether it is merged or not, but I'm just curious.
>
> Thanks.
> I realize this is a customer-driven diff, but if possible, since this is a
> public code base, could you provide some (redacted), public-facing testing
> instructions?
Sure! To test this change you need to:
1. Create a 'subprojects' folder in the root of ubuntu-cve-tracker and, inside this new one, another folder with the name of your subproject. subprojects` function in cve_lib. You need to provide all the mandatory fields. check-syntax to verify that the tool alerts about a missing CVE when cve_triage is set to true and that it doesn't if false.
2. Populate config.yml inside the subproject as needed by `load_external_
3. Run scripts/
> This has no impact on whether it is merged or not, but I'm just curious.
>
> Thanks.