Managing a GitHub Organization: Tools, Tips, and Best Practices
summary
An organization launches its GitHub org 18 months ago and grows to ~30 projects while documenting a ticketing workflow, an internal repo of best practices, and an approval path that routes legal and marketing reviews. Concrete tooling includes DCO enforcement via the org-level GitHub app (and disabling squash merges), Terraform + GitHub provider for repo/team/user as code with a plan/app GitHub Action, repo-inter checks in CI, GitHub Actions for builds/artifacts, a Jekyll landing page, and Grimoire/CHAOSS metrics for community health.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:20Develop a Proposal
- 3:20Workflow for new GitHub projects
- 5:40Open-Source Guidelines
- 6:36Best Practices
- 7:40DCO GitHub App
- 10:06Repolinter GitHub Action
- 11:36Managing GitHub
- 15:32$ terraform plan
- 16:30Managing Users
- 18:10Automate Terraform
- 19:16Build Automation & Artifact Publishing
- 19:57Build & Publish Workflow
- 21:05GitHub Pages & Jekyll
- 22:30Metrics & Analytics
- 23:33Sample metrics
- 24:10Future
- 24:51Resources
related talks
40mA Guide to Securing GitHub Based on Lessons Learned
39mA Guide to Securing GitHub Based on Lessons Learned
36mWhale Care 101 - How We Organize A 200+ Devs Project
39mUsing Github for more than code
45mHow GitHub builds GitHub on GitHub
57mOpen Source at commercial organisations
21mGetting the Most Out of Git
31mHow GitHub Uses GitHub to Build GitHub