Getting the Most Out of Git
summary
Argues for a simple GitHub workflow for most projects (claims 99% of teams don’t need complex branching), recommends protect main branch and basic CI that just verifies apps build or packages compile, uses GitHub/GitLab features like CODEOWNERS, scheduled CI (example: run internal R package builds monthly on the 10th with a 3‑hour fixer assigned), and implements continuous deployment for per‑branch Shiny preview apps that auto‑destroy on merge; these approaches reduce chaos but add maintenance and infrastructure.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:09Git frustrations and workflows
- 3:59Code importance to others
- 6:29Simple Git workflows
- 8:15Protecting main branch with CI
- 11:25Teams with code owners
- 13:11Deploying Shiny apps
- 14:56Pedantic CI checks
- 17:44Scaling Git workflows
- 18:46Summary
- 19:30Q&A
