meedoomostafa/DevDiag

Run DevDiag diagnostic scan and annotate findings in GitHub Actions

Trust Signals

name	description	required	default
path	Path to scan	no	.
profile	Diagnostic profile (e.g., ai-ml)	no	""
rule-pack	Path to an external deterministic rule pack	no	""
redact	Redaction level: default, strict, off	no	default
ci	Force CI/local parity collection and evaluation	no	true
include-hidden	Include low/info and configured hidden findings in rendered and saved reports	no	false
save-report	Save report and upload as JSON artifact	no	true
summary	Write a short GitHub job summary	no	true
fail-on-findings	Fail the action when DevDiag reports high or critical findings (deprecated, use fail-severity)	no	true
fail-severity	Minimum finding severity that fails the action: off, info, low, medium, high, critical	no	high
artifact-name	Name for the uploaded JSON report artifact	no	devdiag-report
format	Output format: github, human, json, ndjson, markdown	no	github
mask-values	Newline-separated literal values to register with GitHub add-mask before running DevDiag	no	""
use-system-devdiag	Whether to prefer using a preinstalled devdiag binary in PATH instead of building from the action source	no	false

name	description
report-path	Path to the generated JSON report artifact
summary-written	Whether the action wrote a GitHub job summary
scan-exit-code	The raw exit code of the devdiag scan command
report-uploaded	Whether the JSON report was uploaded as an artifact
render-exit-code	The exit code of the devdiag report command when save-report is true