GitHub Advanced Security customers can now specify custom patterns for use in private repo secret scanning. When a new pattern is specified, secret scanning searches a repository's entire git history for it, as well as any new commits.
User defined patterns are in beta on cloud and will be available on GHES next quarter. They can be defined at the repository and organization level.
Learn more about custom patterns
Learn more about secret scanning
GitHub Enterprise Server 3.1 is now generally available for all customers. It helps customers work with large, busy repositories, while enabling developers to develop and deploy with less effort than ever.
For more information about GitHub Enterprise Server 3.1, read the GitHub Enterprise Server 3.1 blog post and release notes or download it today.
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.
For more information see "Defining which alert severity levels cause pull request check failure."