GitHub may temporarily require authentication for some public Git-over-HTTPS clones and fetches
GitHub announced that during periods of unusual traffic, it may temporarily require authentication for some clones and fetches of public repositories over HTTPS. The stated purpose is to help protect github.com's availability.
Why it matters
Automated builds, deployment scripts, or CI jobs that clone public repositories anonymously over HTTPS may fail intermittently during these periods. Builders relying on unauthenticated access should plan for credential handling.
Who should care
DevOps engineers, CI/CD maintainers, developers running automated git clones, teams deploying from public repositories
What you can do
Configure a GitHub token or credentials for git operations in CI and deployment scripts so clones and fetches still succeed if authentication is temporarily required.