Skip to main content

Recap and FAQ

Summary: this last lesson condenses the previous 5 into 10 lines, answers the questions beginners ask most (useful for search engines and to lift the last doubts), and points you to the next step.

1. What you know now​

You are not a Git user yet. But you now have the mental foundation to learn the commands quickly and without confusion. It is the difference between reading a road sign and knowing how to drive — you are ready for step two.

2. FAQ · beginners' frequent questions​

These questions come up constantly in forums, on Stack Overflow, on Reddit r/git. Here are short, honest answers.

2.1 Is Git hard?​

Git's concepts are demanding (branches, rebase, merge, conflict resolution) but 90% of daily usage relies on 6 commands: clone, add, commit, push, pull, branch.

Count on 1 to 2 weeks to be comfortable with everyday use, 3 to 6 months to master the complex cases (interactive rebase, cherry-pick, big messy conflict resolution).

2.2 Do I need to know the terminal?​

Yes, a minimum. Git has graphical interfaces (GitHub Desktop, Sourcetree, VS Code's Git tab…) but complex problems (conflicts, history rewriting, remote server operations) are almost always solved on the command line.

The Premium Git Course starts with terminal fundamentals — you are not left alone.

2.3 Git or GitHub? Which should I learn first?​

Git first. GitHub without Git is useless. Git without GitHub is perfectly usable (though less convenient). Understand the tool; the platform will take you 30 minutes.

See lesson 3 for the full distinction.

2.4 Can I learn Git without knowing how to code?​

Technically yes, Git is a file manager with history — it can version documentation, configurations, designs, cooking recipes. Many writers use it for their manuscripts.

But Git's power really shows when used on code, with branches, pull requests, pipelines. If you do not code, aim for a documentation-oriented use instead.

2.5 How much does Git cost?​

Nothing. Git is free, open-source software (GPL v2 licence). You can install it on any machine, personal or professional, at no cost.

The platforms (GitHub, GitLab, Bitbucket) have a free plan that is enough to start. Paying becomes relevant when the team grows or when you want advanced features.

2.6 Is Git secure?​

Yes, twice yes.

  • Integrity: every commit is identified by a cryptographic fingerprint (SHA-1, migrating to SHA-256). It is impossible to modify a commit without its identifier changing — and therefore without the whole rest of the history changing in cascade.
  • Encryption in transit: exchanges with GitHub/GitLab/Bitbucket happen over HTTPS or SSH, encrypted end to end.

Beware nonetheless: Git does not encrypt content at rest in the repository. Never store passwords or API keys in Git — use a secrets manager (dedicated lesson in the DevOps Security course).

2.7 Can Git lose my work?​

Almost never, if you follow two simple rules:

  1. Commit frequently (one per small logical step). A commit is permanent in the history.
  2. Push regularly to a remote (GitHub/GitLab). That way, your work exists in at least two places.

Git even has a rescue command (git reflog) that keeps a local trace of the last 90 days of operations — often allowing you to recover a commit you thought was lost.

2.8 What is the difference between git pull and git fetch?​

  • git fetch = look at what is new on the remote, without integrating anything.
  • git pull = git fetch followed by git merge → directly integrates the news into your local branch.

Recommendation: prefer fetch, then inspection, then a conscious merge. pull is faster but sometimes surprising.

2.9 Can I use Git without internet?​

Yes, almost always. All local operations (commit, branch, merge, log, diff) work offline. You only need internet to synchronize with a remote (clone, push, pull, fetch).

It is one of the big advantages of the distributed model over SVN.

2.10 Does Git replace backups?​

No. Git is not a backup solution:

  • It does not protect against the deliberate deletion of a whole repository.
  • It does not store large binary files efficiently (photos, videos, databases).
  • A single remote repository can disappear if its host shuts down.

Best practice: Git + at least one mirror on another platform + a weekly cold backup for critical projects.

2.11 How long until I am comfortable with Git?​

Here is an honest estimate based on our learners' experience:

StepTypical duration
Understanding the concepts (this discovery course)30 minutes
Using the 6 basic commands5 to 10 hours of practice
Making your first open-source pull request20 to 30 hours
Resolving a complicated conflict without stress1 to 3 months
Teaching Git to someone6 to 12 months

2.12 Do I need a paid GitHub account to start?​

No. GitHub's free plan gives you:

  • Unlimited public and private repositories.
  • 2,000 free GitHub Actions minutes per month for private repositories.
  • GitHub Pages to host a static site for free.
  • Access to millions of open-source projects.

The paid plan becomes useful in a company, not for getting started.

2.13 Is Git compatible with Windows / macOS / Linux?​

Yes, on all three. Git was created by Linus Torvalds for the Linux kernel, but it is just as well supported on:

  • Linux: available in every package manager (apt, yum, pacman…).
  • macOS: shipped with the Xcode developer tools, or via brew install git.
  • Windows: official installer Git for Windows which includes Git Bash — a very handy minimal Unix terminal.

3. Going further​

You have the mental foundation. Three possible directions.

Direction 1 · Learn to use Git (recommended)​

It is the logical continuation of this course. The Premium Git Course covers:

  • Detailed installation and configuration on Windows, macOS, Linux.
  • The 6 essential commands with hands-on exercises.
  • Branches, merge, rebase, cherry-pick, stash, tags.
  • Pull requests, code review, conflict resolution.
  • Team workflows (Git Flow, GitHub Flow, trunk-based development).
  • Real projects end to end.

Direction 2 · Explore the other DevOps foundations​

This discovery course has a cousin for every building block of modern DevOps:

Direction 3 · Jump straight to practice​

Create a free account on GitHub, follow the official Hello World guide (15 minutes), and make your first repository. It is sometimes the best way to anchor the concepts.

4. One last picture to take with you​

Remember in 30 seconds​

  • This course gave you the mental foundation. The commands will come quickly.
  • 90% of Git fits in 6 commands. The remaining 10% is for rare cases.
  • Recommended next step: the Premium Git Course to move to practice, or another discovery course to broaden your DevOps culture.

Congratulations, you have finished the discovery course.

Ready for practice? Discover the Premium Git Course →

Want to explore the other foundations? See all discovery courses →

Last step: take the end-of-course quiz — five corrected and explained questions, three minutes, to check that the essentials are in place.