muno92/ReSharper CLI InspectCode

Inspect code with ReSharper Command Line Tool and annotate PR

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
solutionPath	Path to Solution file to be inspected.	yes	—
failOnIssue	Whether the action should fail if there are any issues.	no	1
version	Version of the Resharper CLI tool to install. Defaults to the latest available.	no	—
minimumReportSeverity	Minimum severity for issues to be reported. Defaults to "HINT". [INFO, HINT, SUGGESTION, WARNING, ERROR]	no	hint
minimumSeverity	Minimum severity for issues to cause the action to fail. Defaults to "notice". Ignored if failOnIssue is set to '0'.	no	notice
exclude	Relative path(s) or file masks that define which files to exclude during the inspection.	no	—
include	Relative path(s) or file masks that define which files to include during the inspection.	no	—
workingDirectory	The working directory in which to run the `jb` command and to which all paths/patterns are relative.	no	—
ignoreIssueType	Comma-separated list of issue types to ignore.	no	—
solutionWideAnalysis	Explicitly enable or disable solution-wide analysis. If not specified, solution-wide analysis will be enabled or disabled based on the existing settings.	no	—
extensions	Comma-separated list of extensions to install.	no	—
noBuild	Let you specify whether to build the target solution before starting the analysis. By default (false), InspectCode always builds the solution.	no	false
cachesHome	Lets you specify a custom location for the data that InspectCode caches.	no	—
properties	Lets you override MSBuild properties. You can use a semicolon to separate multiple properties --properties:prop1=val1;prop2=val2.	no	—
dotnetVersion	Lets you specify the version of the .NET SDK to use.	no	—
verbosity	Sets the verbosity level of the output. [OFF, FATAL, ERROR, WARN, INFO, VERBOSE, TRACE]	no	—

Outputs

no outputs