Introducing GitHub Sudo Mode
In the ongoing effort to keep our users safe, we recently took inspiration from the Unix sudo command. We wanted to require password confirmation for dangerous actions on GitHub.com, but…
In the ongoing effort to keep our users safe, we recently took inspiration from the Unix sudo command. We wanted to require password confirmation for dangerous actions on GitHub.com, but we didn’t want to force you to be constantly entering your password.
Meet GitHub’s “sudo mode”
Dangerous actions (e.g. adding email addresses or public keys) will now require password confirmation. If you’re deep in the zone and you’re doing a lot of these dangerous actions, we’ll only ask you to re-authenticate every few hours.
With this balance of security and convenience, we help you keep your account safe, without getting in your way. Feedback is always welcome. Enjoy!
Written by
Related posts
What’s coming to our GitHub Actions 2026 security roadmap
A look at GitHub Actions’ 2026 roadmap, outlining how secure defaults, policy controls, and CI/CD observability harden the software supply chain end to end.
Updates to GitHub Copilot interaction data usage policy
From April 24 onward, interaction data—specifically inputs, outputs, code snippets, and associated context—from Copilot Free, Pro, and Pro+ users will be used to train and improve our AI models unless they opt out.
GitHub availability report: February 2026
In February, we experienced six incidents that resulted in degraded performance across GitHub services.