Heidelberg AICurriculum

Git Crash Course - Full Tutorial For Beginners

NeuralNine ·2026-06-26 ·1 min read

Summary written by us from the video's transcript. The video, and everything in it, is NeuralNine's work.

Learn the fundamentals of Git, from initializing a repository to committing, pushing, pulling, and handling basic conflicts, using concrete command‑line examples.

Takeaways

  • Git tracks incremental changes locally, enabling easy rollback and collaboration.
  • `git add`, `git commit -m`, and `git push` are the core workflow for recording and sharing work.
  • Use `git status` and `git diff` to understand what’s changed before committing.
  • `git restore --staged` removes files from the staging area; `git restore` discards unstaged edits.
  • `git pull` fetches remote changes and merges them, but uncommitted local edits can cause conflicts that must be resolved.

What Git Is and Why It Matters

Git is a core version control system that tracks incremental changes in your code, allowing you to revert, view diffs, and collaborate without manually copying directories or sending files via email. Unlike hosting platforms such as GitHub, GitLab, or Bitbucket, Git runs locally and provides the underlying functionality for those services.

Creating a Repository and Cloning It Locally

Create an empty repository on GitHub (or any host) – set visibility to private if you want to test authentication. Generate a personal access token (classic) with full permissions, copy it, and use HTTPS URLs that embed the token (e.g., `https://<token>@github.com/username/repo.git`). Run `git clone <url>` in your chosen directory to obtain a local copy.

Adding Files, Staging, and Committing

Use `git status` to see untracked files. Stage changes with `git add <file>`. After staging, `git status` shows “changes to be committed.” Commit with `git commit -m "initial commit"`; you can also omit `-m` to open an editor for the message. Configure your identity once with `git config user.name "Your Name"` and `git config user.email "you@example.com"`.

Pushing Changes to the Remote

After a successful commit, synchronize the local branch with the remote using `git push`. For a brand‑new repository this also creates the remote `main` branch. Refresh the GitHub page to see the new file and commit history.

Modifying Files, Viewing Diffs, and Restoring

Edit files, then run `git status` to view modified and untracked items. Use `git diff` to see line‑by‑line changes before committing. To undo staged additions, `git restore --staged <file>`; to discard unstaged edits, `git restore <file>`.

Pulling Updates and Resolving Simple Conflicts

Clone the same repository in a second directory to simulate another developer. After making and pushing changes there, return to the first clone and run `git pull` to fetch and merge remote updates. If local uncommitted edits conflict with incoming changes, Git reports a conflict; you can resolve it by committing or discarding your local modifications before pulling again.