GitHub on YouTube · Open on YouTube
Professional practice · Competent · Lesson 40 of 98 · 8 min video, then about 6 hours of practice
Continuous integration with GitHub Actions
After this you can set up a pipeline that lints, type-checks and tests every pull request and blocks merging when anything fails.
Why it matters
CI is the team's shared guarantee that main always works. Every pull request runs the same checks on a clean machine, so 'works on my machine' stops being an argument. Start with lint, type-check and unit tests on every pull request, then add end-to-end tests. Protect the main branch so nothing merges red. Trap: a pipeline so slow people stop waiting for it. Keep it under ten minutes.
How to use this resource
GitHub's own short introduction. Enough to set up your first pipeline.