| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…uality-queries` For backwards compatibility. We should remove this once `quality-queries` is no longer in use.
Replaces the synthetic value for `analysisKinds`
| - `code-quality`: Analysis focused on code quality. This must be enabled in conjunction | ||
| with `code-scanning`. |
There was a problem hiding this comment.
Out of interest, where's this restriction coming from? We can address it in a follow up PR, but I think we want to be able to run code quality only analyses.
Sorry, something went wrong.
There was a problem hiding this comment.
Yes, this restriction will be lifted in a follow-up PR. It's just representative of the current state of the implementation as of this PR.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR follows up from #3055 and adds an analysis-kinds input to the init action. This is a required input, but defaults to code-scanning so that there's no change to existing workflows. The input is parsed and the resulting analysis kinds are stored in the configuration.
The isCodeQualityEnabled function is updated to inspect that configuration, instead of the quality-queries input.
For backwards compatibility, we enable the code-quality analysis kind if there is an input to quality-queries.
Fundamentally, this PR shouldn't change the existing behaviour of the Action in any way.
Risk assessment
For internal use only. Please select the risk level of this change:
Merge / deployment checklist