ci: move pvsStudio job to its own workflow & use new flag #2210
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The license will expire in approximately 1 month. I disabled the expiration check for the moment.
Actually my plan is to disable this workflow by following this guide afterwards:
https://docs.github.com/en/[email protected]/actions/managing-workflow-runs/disabling-and-enabling-a-workflow
At the moment we are not benefinit from running PvsStudio on CI, because we are not analysing the results from the PVS Studio report automatically. The issue #2074 describes some of the ideas we could apply there. Until that work is addressed I think it will be better to disable this workflow.