Control which code scanning alerts cause a pull request check to fail

You can now configure which code scanning alert severity levels cause a pull request check to fail. This lets you prevent pull requests that generate alerts with chosen severity levels from being merged into your codebase.

This is set at repository level, and lets you define whether alerts with severity error, warning, or note will cause a pull request check to fail.

By default, code scanning alerts with severity error will cause a pull request check failure.

Screenshot 2021-06-02 at 10 24 02

For more information see "Defining which alert severity levels cause pull request check failure."

On June 5th, 2021 the GitHub Container Registry, ghcr.io, will be put into maintenance mode. The maintenance window will occur from 16:00 – 17:30 UTC. During this short time pushes to the service will be blocked, however pulls or downloads will remain available. For more detailed status information during maintenance, please refer to https://githubstatus.com

Learn more about GitHub Container Registry

For questions, visit the GitHub Packages community

To see what's next for Packages, visit our public roadmap

See more