Skip to main content

Git in CI/CD and open source

Summary: in the modern world, a simple git push automatically triggers a whole chain: tests, quality analysis, security, Docker image build, production deployment. This lesson describes that pipeline step by step, then explains how the same mechanism allows strangers to contribute to Linux, React or Python.

1. The push that triggers everything​

In 2005, a git push merely updated the remote server. In 2026, on a modern project, it triggers complete automation.

What to remember:

  • Git is the entry point of the pipeline. Nothing starts until there is a git push.
  • Each job (compilation, tests, security…) runs in parallel, on ephemeral servers provisioned on demand.
  • A failure blocks the merge: code cannot reach main if it does not pass the checks.
  • This mechanism is the foundation of modern DevOps. Without it, no continuous deployment is possible.

2. A pull request enriched by CI​

On GitHub or GitLab, the pull request view displays all the pipeline results as green checks or red crosses.

It is this automatic feedback that makes a modern team fast and reliable at the same time. Teams deploy several times a day because the pipeline catches the problems before humans do.

3. GitOps — when Git becomes the single source of truth​

There is an even more recent practice, called GitOps, where the infrastructure itself (servers, networks, Kubernetes configurations) is described in Git files. A modification of a YAML file automatically triggers reprovisioning.

The founding principle of GitOps:

If it is not in Git, it does not exist.

All infrastructure modifications must go through a commit. No more "it worked last week but nobody knows why it is broken now" — the Git history is the single source of truth.

GitOps is covered in depth in the premium courses Argo CD and Flux CD, which are the two dominant tools in the field.

4. Contributing to an open source project​

The same mechanism (Git + pull request + CI) allows millions of strangers to contribute to the largest open source projects (Linux, React, Kubernetes, Python…). The workflow is called fork + pull request.

This workflow is the foundation of all modern open source. Without it, no individual could propose a fix to Linux or Python. The entry barrier would be insurmountable.

5. My first open source contribution, stress-free​

Here is a checklist for a successful first contribution, tested on hundreds of learners.

Where to find an accessible project to get started:

  • goodfirstissue.dev — aggregates beginner-friendly tickets across all of GitHub.
  • up-for-grabs.net — directory of projects open to contributions.
  • The projects of your favourite tools: Docusaurus, Nginx, VS Code all have good first issue tickets.

What contributing brings you:

  • A visible line on your GitHub profile — checked by recruiters.
  • Real experience of the team workflow — even if you are alone at your desk.
  • A rare skill: the ability to work with code you did not write.

6. The cultural lesson: Git industrialized cooperation​

Let us step back. Before Git, contributing to software you had not written yourself was a feat. You had to know the author, obtain rights, understand their system, avoid overwriting their work.

After Git, in 2026:

Nobody could have imagined these numbers before 2005. Git is not just a technical tool. It is a social infrastructure.

Remember in 30 seconds​

  • A git push in 2026 automatically triggers compilation, tests, security, deployment.
  • Pull requests display the CI results line by line — feedback is instant.
  • GitOps applies the same principle to infrastructure: Git becomes the single source of truth.
  • The fork + pull request workflow allows strangers to contribute to the world's biggest projects.
  • Your first open source contribution is more accessible than you think — search for good first issue on GitHub.

Next: Recap and FAQ →