audit-publish

Converting audit report findings into GitHub issues is done by parsing the report and using the GitHub API to create tracked entries. This process includes deduplication, label reconciliation, and completeness checks to ensure accuracy.

Audit report deduplication works by comparing new findings against existing GitHub issues before creation. This prevents duplicate entries, ensuring that only unique findings are tracked and resolved in the repository.

Yes, you can use the GitHub CLI to automate issue tracking from audit reports. The process requires access to the GitHub API and relies on the gh dependency to create, label, and manage the issues.

The best way to ensure all audit findings are published is by using a completeness gate. This mechanism checks processed issues against a completeness checklist, verifying that every finding is accurately converted and labeled.

Yes, you need a specific audit report format to create GitHub issues. The conversion process requires knowledge of the audit report structure to accurately parse findings and map them to the correct issue labels and severity.

Severity and domain labels are reconciled by mapping the parsed audit findings to the existing label schema in your repository. This ensures that each created issue is categorized correctly based on its severity and domain.