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
Let’s talk about GitHub Actions
A look at how we rebuilt GitHub Actions’ core architecture and shipped long-requested upgrades to improve performance, workflow flexibility, reliability, and everyday developer experience.
GitHub Availability Report: November 2025
In November, we experienced three incidents that resulted in degraded performance across GitHub services.
The new identity of a developer: What changes and what doesn’t in the AI era
Discover how advanced AI users are redefining software development—shifting from code producers to strategic orchestrators—through delegation, verification, and a new era of AI-fluent engineering.