The Unified Build, Test, and Install reusable GitHub actions workflow is becoming the main workhorse for CI. Currently, unlike the "Build and Test" action, this does not support running clang-tidy. Extend this so that clang-tidy can be run, ideally optionally.
Ideally, this is handled via an additional input to the workflow_call. I think we get up to 100 inputs for a workflow_call, while a workflow_dispatch is limited to 10. (Or so the LLMs claim...) It is fine if this is not easily accessible via the workflow_call.
The Unified Build, Test, and Install reusable GitHub actions workflow is becoming the main workhorse for CI. Currently, unlike the "Build and Test" action, this does not support running clang-tidy. Extend this so that clang-tidy can be run, ideally optionally.
Ideally, this is handled via an additional input to the
workflow_call. I think we get up to 100 inputs for aworkflow_call, while aworkflow_dispatchis limited to 10. (Or so the LLMs claim...) It is fine if this is not easily accessible via theworkflow_call.