As announced last year, and after two brownouts to raise awareness, GitHub has now removed support for the Subversion protocol on github.com. It will also be disabled in GitHub Enterprise Server 3.13, scheduled for release in June 2024. Please be aware that the GitHub Importer supports migrating Subversion repositories to Git on GitHub.
If you are signed into multiple accounts on GitHub.com, you'll be able to pick between them when you sign in using the device flow. This authentication method is typically used for console applications, like the GitHub CLI and remote use of VS Code.
For more information about using multiple accounts, see "Switching between accounts".
GitHub secret scanning protects users by searching repositories for known types of secrets such as tokens and private keys. By identifying and flagging these secrets, our scans help prevent data leaks and fraud.
We have partnered with Canva to scan for their tokens to help secure our mutual users in public repositories. Canva tokens enable users to perform authentication for their Canva Connect API integrations. GitHub will forward any exposed tokens found in public repositories to Canva, who will then rotate the token and notify the user about the leaked token. Read more information about Canva tokens.
GitHub Advanced Security customers can also scan for and block Canva tokens in their private repositories.