within user request, we write out json files
(bom.json, .build-config.json) by model_dump_json()method, but with no indentation so the output is a huge one-line file
[x] Code coverage from testing does not decrease and new code is covered
[n/a] Docs updated (if applicable)
[n/a] Docs links in the code are still valid (if docs were updated)
Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:
within user request, we write out json files (bom.json, .build-config.json) by
model_dump_json()
method, but with no indentation so the output is a huge one-line fileunlike generating data in integration tests: https://github.com/containerbuildsystem/cachi2/blob/main/tests/integration/utils.py#L228
Maintainers will complete the following section
Note: if the contribution is external (not from an organization member), the CI pipeline will not run automatically. After verifying that the CI is safe to run:
/ok-to-test
(as is the standard for Pipelines as Code)