A small team starts a new project on GitHub. They want CI. They look at the options.
Setting up Jenkins means a server, an SSL cert, a database, plugin patching, backups. GitLab CI means moving the repository. The newer SaaS options need accounts, credit cards, third-party reviews. The team groans — they just wanted tests to run.
Then they notice: GitHub itself has a CI service built in. A YAML file in
.github/workflows/ and on every push the tests run, the build happens,
and the result appears as a check on the pull request. No new servers. No new
credentials. The CI is the repository.
That’s GitHub Actions. It is now the default CI on open source and on a growing majority of new private projects.