Audit GitHub Code Quality finding dismissals and reopenings
Summary
You can now review manual dismissals and reopenings of GitHub Code Quality findings in your organization or enterprise audit log. Findings may appear in either your repository’s default-branch backlog or… The post Audit GitHub Code Quality finding dismissals and reopenings appeared first on The GitHub Blog .
Original Text
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> You can now review manual dismissals and reopenings of GitHub Code Quality findings in your organization or enterprise audit log. Findings may appear in either your repository’s default-branch backlog or pull requests. Two new events record these actions:
repo.code_quality_findings_dismissed records a dismissal of one or more backlog findings.
repo.code_quality_findings_reopened records a reopening of one or more backlog findings.
Each event includes who made the request, when it happened, the repository and rule, and the identifiers and count of the affected findings.
For repositories with Code Quality enabled, you don’t need additional setup. If you have access to your organization audit log or enterprise audit log, filter by these action names to review activity. On GitHub Enterprise Cloud, you can also retrieve these events through the audit log API.
This improvement is generally available on GitHub Team and GitHub Enterprise Cloud, including enterprises with data residency. It isn’t available on GitHub Enterprise Server. For more on managing findings, see Fixing code quality findings in your repository backlog.
Join the GitHub Community discussion.
The post Audit GitHub Code Quality finding dismissals and reopenings appeared first on The GitHub Blog.
Lotu Radar provides attributed news summaries and links to the original publisher. Full reporting and copyright remain with the source.