We have shipped improvements to the code scanning alerts branch filter! These changes make it clearer which code scanning alerts are being displayed on the alerts page.
By default, the code scanning alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar.
We have simplified the search syntax to the format branch: You can use this syntax multiple times in the search bar to filter on multiple branches. The previous syntax ref:refs/heads/[branch name] is still supported, so any saved URLs will continue to work.
In May we announced that GitHub Advisory Database now includes Go advisories. Today we're excited to announce that all of GitHub's supply chain security features are available for Go modules, which will help the Go community discover, report, and prevent security vulnerabilities.
Learn how each of GitHub’s supply chain security features works with Go modules on the GitHub blog.
🌏 Today we're releasing a new beta feature that allows you to translate GitHub Discussions content into different spoken languages. This initial beta release includes support for Korean, Brazilian Portuguese, and English, and we plan to add support for more languages soon.
This beta feature is now enabled for all users. To try it out, configure your web browser with Korean or Brazilian Portuguese as the default language, then navigate to any GitHub repo that has Discussions enabled. Click the overflow menu beside any discussion comment and you'll see a link to translate it to your preferred language:
To see some popular communities using GitHub Discussions, check out docs.github.com/discussions.
We'd love to hear what you think of this new feature and how it can be improved. Please join the discussions below to share your feedback.