Closed github-actions[bot] closed 1 month ago
Hi @github-actions[bot]. Thanks for your PR.
I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/packit build
/packit retest-failed
/packit retest-failed
Updates upstream OSCAL content
Auto-generated by the update-oscal workflow.