#git (2024-03)
All things git (except gitops)
2024-03-05
2024-03-13

We’re checking if moving to Github Enterprise is a good thing, and how the migration experience is (mostly moving all the non-company user accounts to a company sso-backed user account). Any feedback appreciated

@Erik Osterman (Cloud Posse) fyi ^^

Office hours?


Knowing what I know now, I truly see how “GitHub Teams” is for small teams, where you really don’t need/expect strict controls around workflows and approvals, secrets, branch protections, audit trails, etc. GHE has added some real differentiators that makes GHE a must-have.
• Organizational Rule Sets
• Secrets Tied to Branches via Environments
• Internal repos for private actions and shared workflows
• Environment protection rules that require (e.g. smoketests) checks to pass prior to approval

In teams, for example, any one with write
access to a repo can exfiltrate any secret. End of story.