GitHub secret scanning protects users by searching repositories for known types of secrets. By identifying and flagging these secrets, we help protect users from data leaks and fraud associated with exposed data.
We have partnered with SendGrid to scan for their access tokens, which allow users to retrieve account information and statistics. We'll forward access tokens found in public repositories to SendGrid. SendGrid will then either suspend the detected token or send it to their fraud team for manual review, depending on the token scope. More information about SendGrid API tokens can be found here.
GitHub Advanced Security customers can also scan for SendGrid's API keys and block them from entering their private and public repositories via secret scanning’s push protection feature.
Learn more about secret scanning
Partner with GitHub on secret scanning
As you are aware, we have recently introduced new issues close states. When closing an issue, you can opt to close as 'complete' (default option) or 'not-planned'.
We have now made changes to our GitHub app in Slack and Microsoft Teams to reflect the new issue close states.
For more information, see GitHub for Microsoft Teams or GitHub for Slack.
GitHub Mobile can no longer connect to GitHub Enterprise Server 3.0. To enable connections from GitHub Mobile to GitHub Enterprise Server, a site administrator must upgrade to GitHub Enterprise Server 3.1 or later. Newer versions of GitHub Enterprise Server improve performance, enhance security, and provide new features. For more information, see "GitHub Enterprise Server releases" and "Upgrading GitHub Enterprise Server."
Read more about GitHub Mobile and send us your feedback to help us improve.