Re:Securing a GitHub repo is a ton of work
by no-reply on Friday October 21, 2022 @02:17AM
(#33285095)
Won't have to worry about compliance if you are forced to comply every hour /s
When working on open source software and collaborating via public GitHub, you can almost forget that git is a distributed version control system.
But in the restricted corporate setups you describe, git's distributed nature shines.
They can lock down internal GitHub as much as they want to, but that won't keep you from making local commits, or exchanging commits directly with your coworkers while developing.
It's not that hard really. They just put in draconian restrictions and remove all of your agency as a user. You can push commits, new branches, and open pull requests. That's about it.
Want to merge? Restricted. Make a new repo? Restricted. Use a GitHub Action? Restricted. CODEOWNERS? Restricted. Branch filters? Restricted. Forks? Restricted. Releases, packages, artifacts, security, insights, settings, webhooks, environments, pages, wiki, issues? Restricted. Access a repo you aren't already a member of? Restricted. Protected tags, dependency graph, dependabot, code scanning, secret scanning, deploy keys, secrets, github apps, oauth, notifications? Restricted. Stars? Restricted. And your SSO token expires every hour.
There! Now we're so secure we can't do any work.