Git in Practice #1: What Is Git, and Why Use It?

In this first chapter, we answer two questions: what is Git, and why use it? What you'll learn What Git is, and the problem it solves Why every developer uses it, alone or in a team The difference between Git and GitHub The videos of this course are in French. Turn on YouTube’s auto-translated subtitles if needed: every chapter below is fully written in English. ...

November 19, 2026 · 2 min · 360 words · Naimi

Git in Practice #4: git init and Your First Push to GitHub

In the previous chapter, the project already existed on the server. Here, we start from an empty folder: we initialize Git, then send the project to GitHub. What you'll learn Turn an existing folder into a Git repository with git init Create the repository on GitHub and understand .gitignore Link your project to the repository with git remote Make the first commit and the first push 1. Initialize Git: git init Create a folder with a first file, then initialize Git inside it: ...

November 19, 2026 · 4 min · 689 words · Naimi

Mini Library Course #4: Version Your Symfony Project with Git & GitHub

Before adding new features, we take a moment to push our code to GitHub. Versioning your work regularly is a good habit: it keeps a clean history, lets you go back if something breaks, and protects the work already done. What you'll learn ...

November 18, 2026 · 3 min · 604 words · Naimi

Git in Practice #8: Pull Requests and Forks on GitHub

In the previous chapter, we covered branching strategies. Here, we get concrete, from the developer’s side, based on Git Flow. What you'll learn What a pull request is, and what a fork is Contribute to a project you don’t own How a code review works Pick the right merge option The problem I created my branch from develop, finished my work and pushed it. Now what? ...

November 19, 2026 · 4 min · 653 words · Naimi

Git in Practice #9: Syncing Your Fork with upstream

In the previous chapter, we covered pull requests and forks. But one very important point was missing: how do you get the original project’s new changes into your fork? What you'll learn Why your fork falls behind the original project The role of the origin and upstream remotes Keep your fork up to date, and the full contribution cycle The problem Your fork is a copy of the project, taken at a given moment. While you work, other developers get their pull requests merged into the original project. Your fork doesn’t update itself. ...

November 19, 2026 · 3 min · 468 words · Naimi