Git from Scratch to Confident Developer

Master Git to work confidently in a team, manage project history effectively, and succeed in technical interviews — from your first commit to pull requests in a real repository.

13 강의 5시 42분 구독 포함

이 강좌는 누구를 위한 것인가

Beginner programmers who already code in any language but have never seriously worked with version control systems or have only superficial knowledge of Git and want to structure their knowledge before entering the job market.

요구사항

Basic command line skills: navigating between directories, creating and deleting files. Ability to write simple code in any programming language — the specific language doesn't matter, what's important is that you already have some programming experience.

강좌 커리큘럼

13 강의

소개 Introduction: Git from Scratch to Confident Developer

1 Git from Novice to Confident Developer 32.832초

2 Without Git: Chaos. With Git: Control. 33.912초

3 This course is for you if... 30.576초

4 After this course you'll be able to... 37.008초

5 Sections 1–3: From 'why do I need this' to your first meaningful commit 30.888초

6 Sections 4–6: Commit History, Branches, and Safe Error Recovery 33.576초

7 Sections 7–9: GitHub, Team Collaboration, and Handling Conflicts with Confidence 36.288초

8 Sections 10–12: Workflows, Advanced Tools, and Final Project 27.144초

9 How to Learn for Lasting Knowledge 28.656초

6 분

무료 시청

Why Git is Essential - And Why It's a Job Requirement

We'll begin not with commands, but with the pain: exploring what development looks like without version control - folders named 'project_final_2', 'project_final_REALLY_FINAL' and the fear of deleting the wrong thing. You'll understand exactly what problem Git solves, why it became the industry standard, and what employers specifically look for when reviewing your GitHub profile.

version control system change history distributed architecture

22 분

가입 후

Installation and Setup: Getting Git Ready for First Use

Install Git on Windows, macOS, and Linux, and explore why configuring your name and email isn't just a formality but an integral part of commit history. Set up a user-friendly terminal and several useful aliases to work comfortably from day one, rather than struggling with lengthy commands.

Git installation git config global configuration

18 분

구독 포함 구독 신청

First Repository: init, add, commit, and the Magic of the Index

We'll create our first repository and immediately encounter a concept that many struggle with for years - the staging area (index). We'll explore why this 'intermediate layer' between the working directory and history is essential, and through examples, we'll see how the two-step add → commit system results in meaningful, deliberate commits rather than random ones.

repository staging area commit

1 Creating Your First Repository 34.704초

2 Under the Hood of .git 37.992초

3 Hands-on: Creating a Repository 35.664초

4 The Three File States: Why It Matters 40.824초

5 Working Directory: Where the Magic Happens 38.232초

6 The Index: Staging Changes in Meaningful Chunks 28.248초

7 Commit: Preserving History Forever 39.672초

8 The Git Index: A Staging Area for Commits 34.272초

9 Adding a Specific File to the Staging Area 32.208초

10 Adding All Modified Files 39.432초

11 What is a Git Commit? 35.016초

12 Creating Your First Commit 32.784초

13 How to Write Good Commit Messages 36.888초

14 The Problem of Mixed Changes 35.712초

15 Git add -p in Action 40.728초

16 How to Read Patches 37.728초

17 Why Commit Without Add Doesn't Work 29.616초

18 One Task, One Commit 31.512초

19 Commit Messages That Make Sense a Year Later 32.784초

20 Creating Your First Repository 36.216초

21 The Staging Area: Between Code and Commit 29.112초

22 Crafting a Meaningful Commit 29.832초

23 Your First Commit: What's Next? 37.344초

28 분

구독 포함 구독 신청

Reading History: log, diff, show and Navigating the Past

Project history isn't just a log—it's documentation of decisions. Learn to read history informatively: filter commits, examine changes between versions, and understand SHA-1 hashes without fear. We'll explore how to distinguish 'good history' from 'garbage history'—this directly impacts how you're perceived in a team.

commit hash git log git diff

25 분

구독 포함 구독 신청

Branches: The Parallel Reality of Your Code

Branches are the heart of Git, yet they're where many beginners start to feel overwhelmed. We'll demystify branches by showing that a branch is simply a pointer, not a copy of files. We'll cover how to create branches, switch between them, and merge changes, along with exploring the difference between fast-forward and three-way merges using practical examples.

branch HEAD merge

1 The Myth of File Copying in Branches 25.56초

2 How Branches Work Under the Hood 24.336초

3 A Bookmark, Not a Book Copy 25.872초

4 Creating a Branch in Practice 37.344초

5 How Git Branches Work 24.12초

6 Creating a New Branch 31.488초

7 Quick Branch Creation and Switching 27.192초

8 What Happens When Switching Branches 33.672초

9 When Branch Merging Happens Without Conflicts 33.936초

10 How Fast-Forward Merge Works 29.976초

11 Practical Example: Merging a Feature into Main 37.752초

12 When Automatic Branch Merging Fails 27.264초

13 What a Merge Conflict Looks Like 32.52초

14 Steps to Resolve a Conflict 35.688초

15 Why Doesn't a Simple Merge Always Work? 28.608초

16 How Three-Way Merge Works 33.648초

17 Creating a Merge Commit in Practice 30.048초

18 How Delayed Merging Increases Complexity 31.968초

19 The Danger of Ignoring Merge Conflicts 33.168초

20 The Right Way to Resolve Conflicts 33.888초

21 Creating a Feature Branch for a New Task 32.688초

22 Parallel Work in Multiple Branches 40.92초

23 Merging Changes with the Main Branch 41.52초

24 Summary: Branches and Merging 43.944초

32 분

구독 포함 구독 신청

Undoing Mistakes: restore, reset, revert — Doing It Right and the Dangers

One of the most frequently discussed topics in job interviews and practical work is how to undo what's already been done. We'll examine three tools with different 'depths' of undoing and focus on what matters most: demonstrating specific scenarios where reset --hard can disrupt teamwork, while revert offers a safer alternative. We'll explore good and bad solutions with real-world consequences.

git restore git reset git revert

30 분

구독 포함 구독 신청

GitHub and Remote Repositories: Your Code in the Cloud

Making the leap from local to collaborative work: understand what a remote is, how to connect your local repository to GitHub, and the key differences between push, pull, and fetch – the three most commonly confused commands. Special focus on SSH key authentication, as employers expect you to set this up independently.

remote origin push / pull / fetch

27 분

구독 포함 구독 신청

Team Collaboration: Forks, Feature Branches, and Pull Requests

This section covers the workflow used by 90% of open-source and corporate teams. We'll go through the complete cycle: fork → feature branch → commits → pull request → code review → merge. We'll specifically examine how to write PR descriptions that give reviewers immediate context, and which common PR mistakes immediately identify a newcomer.

fork pull request code review

33 분

구독 포함 구독 신청

Merge Conflicts: Don't Panic - Understanding and Resolving Them

Conflicts can be intimidating for beginners, but after this section, you'll face them with confidence. We'll explore why conflicts occur (Git can't read minds - it doesn't know which change is more important), how to read conflict markers, and how to choose the right solution. We'll demonstrate two approaches: manual resolution and using merge tools.

merge conflict conflict markers conflict resolution

28 분

구독 포함 구독 신청

Git Workflows in Real Teams: Choosing the Right Approach

A common interview question is: 'Which Git workflow have you used?' After this section, you'll have a thorough and honest answer. We'll examine three popular approaches — Feature Branch Workflow, Git Flow, and Trunk-Based Development — and explore where each one works well and where it might become a bottleneck.

Feature Branch Workflow Git Flow Trunk-Based Development

23 분

구독 포함 구독 신청

Advanced Tools: Rebase, Stash, Cherry-pick and Tags

Moving on to the tools that distinguish a confident Git user from someone who only knows the basics. We'll explore rebase as an alternative to merge - showing when it makes history cleaner and when it turns it into a nightmare. We'll add stash for quickly 'shelving' unfinished work, cherry-pick for precisely transferring commits, and tags for marking releases.

git rebase git stash git cherry-pick

35 분

구독 포함 구독 신청

Final Project: Simulating Real Team Development

Apply everything you've learned in a cohesive scenario: you're a developer in a small team that needs to add a new feature, fix a bug, and release an update. We'll walk through the complete cycle step by step: creating a repository, working in branches, pull requests, intentionally created conflicts and their resolution, rebasing to clean up history, and final release tagging. By the end, you'll have a real repository that you can showcase to potential employers.

Complete Git workflow Team development Release cycle

35 분

구독 포함 구독 신청