เชฌเชงเชพ เชเซเชถเชฒเซเชฏเซ
Git & Version Control
Track code changes, collaborate with teams, manage branches
โฌข เชเชฟเชฏเชฐ 3เชเซเชเชจเชฟเชเชฒ
+$10k-
เชชเชเชพเชฐ เชชเชฐ เช
เชธเชฐ
3 เชฎเชนเชฟเชจเชพ
เชถเซเชเชตเชพเชจเซ เชธเชฎเชฏ
เชฎเชงเซเชฏเชฎ
เชฎเซเชถเซเชเซเชฒเซ
12
เชเชฐเชฟเชฏเชฐ
เชเช เชจเชเชฐเชฎเชพเช
Git is the universal VCS for code collaboration. Career path: L1 (basic commits, push/pull, branches, pull requests) in month 1 โ L2 (rebase, cherry-pick, merge conflict resolution, git workflows, squashing) by month 2 โ L3 (Git hooks, submodules, monorepo strategies, Git internals, release management, trunk-based development) by month 3. Every developer uses Git daily; proficiency adds $10kโ$25k across all engineering roles. Mastery = seamless code integration, zero merge disasters, and team velocity.
Git & Version Control เชถเซเช เชเซ
Git is the version control standard. Essential for ALL engineering roles, adds $10k-$25k to entry-level salaries. Boost: +$10k-$25k | Learning: Easy-Medium
๐ง เชเซเชฒเซเชธ เช
เชจเซ เชเชเซเชธเชฟเชธเซเชเชฎ
Git CLIGitHubGitLabBitbucketGiteaSourcegraphGitKrakenSublime MergelazygitGitHub Desktopgh CLIhub CLIpre-commitconventional-commitsHusky
๐ฐ เชชเซเชฐเชฆเซเชถ เชชเซเชฐเชฎเชพเชฃเซ เชชเชเชพเชฐ
| เชชเซเชฐเชฆเซเชถ | เชเซเชจเชฟเชฏเชฐ | เชฎเชงเซเชฏเชฎ | เชธเชฟเชจเชฟเชฏเชฐ |
|---|---|---|---|
| USA | $80k | $120k | $160k |
| UK | ยฃ50k | ยฃ75k | ยฃ95k |
| EU | โฌ55k | โฌ80k | โฌ105k |
๐ เชชเซเชฐเชฎเชพเชฃเชชเชคเซเชฐเซ
๐ฏ Git & Version Control เชจเซ เชเชชเชฏเซเช เชเชฐเชคเซ เชเชฐเชฟเชฏเชฐ
โ เชธเชพเชฅเซ เชธเชฐเชเชพเชฎเชฃเซ เชเชฐเซ
โ FAQ
When should I merge vs rebase?
Merge creates a merge commit (preserves history, shows collaboration points). Rebase replays commits on top of another branch (linear history, cleaner logs). Rule: rebase for local branches before pushing (interactive rebase cleans up); merge for integrating shared branches. Trunk-based dev uses rebase for feature branches โ main, no merge commits. Never rebase after pushing to shared branches, causes conflicts for teammates.
How do I recover deleted commits or lost work?
Git reflog saves every HEAD movement for 90 days. Run `git reflog` to see all commits, find the lost SHA, then `git reset --hard <sha>` or `git checkout <sha>` to recover. For deleted branches, `git fsck --lost-found` finds dangling commits. Pro tip: always tag releases and important commits so they survive garbage collection.
What's the difference between monorepo and polyrepo?
Monorepo = one Git repo for many services (shared history, atomic commits across projects, easier refactoring; tools: Nx, Turborepo, Bazel). Polyrepo = separate repos per service (independent CI/CD, easier access control, slower refactoring across projects). Monorepo wins for startups/cohesive teams; polyrepo for large companies/security boundaries. Git handles monorepos fine; tooling (workspaces, CI filters) is the challenge.
How do I handle merge conflicts efficiently?
Conflicts arise when both branches modify the same line. Use `git status` to see conflicts (marked <<<<<<< ======= >>>>>>>). Tools help: `git mergetool` (opens UI), VS Code's Merge Editor (built-in, interactive), or `git diff --ours/--theirs` to see both versions. Always understand the conflict, not just pick 'ours'. Use `git merge --abort` to bail out. Prevention: rebase frequently, small PRs, communicate with teammates.
Should I use trunk-based development or gitflow?
Trunk-based (main only, short-lived branches): high velocity, low merge pain, suitable for continuous deployment. Gitflow (main + develop + release/hotfix branches): clear separation, structured release cadence, bureaucratic. Pick trunk for startups/fast teams; gitflow for regulated/large orgs with formal releases. Most successful tech companies (Google, Meta) use trunk-based.
How do I manage large files and binary assets?
Git is bad at large files (clones are slow, disk bloat). Use Git LFS (Large File Storage) to store pointers instead of actual files. Enable with `git lfs install`, then `git lfs track '*.psd'` etc. For images/videos, consider cloud storage (S3, Cloudinary) + Git-tracked metadata files. Never commit binaries >100MB without LFS; clone times explode.
Can AI help write commit messages?
Yes (2026). Tools like Conventional Commits linters (Husky + commitlint) enforce format automatically. GitHub Copilot can suggest messages; some IDEs (VS Code, JetBrains) integrate AI. Best practice: use `git commit` with a template (`commit.template` in .gitconfig) that prompts for type/scope/subject/body. Conventional format (`feat: add login`, `fix: typo in README`) is machine-readable for changelog generation + semantic versioning.
เชเชพเชคเชฐเซ เชจเชฅเซ เชเซ เช เชเซเชถเชฒเซเชฏ เชคเชฎเชพเชฐเชพ เชฎเชพเชเซ เชเซ?
เชเชฐเชฟเชฏเชฐ เชฎเซเช เชเซเชธเซเช เชเชชเซ โ เช เชฎเซ เชฏเซเชเซเชฏ เชเซเชฐเซเชเซเชธ เชธเซเชเชตเซเชถเซเช.
เชฎเชพเชฐเชพ เชถเซเชฐเซเชทเซเช -เชซเชฟเช เชเซเชถเชฒเซเชฏเซ เชถเซเชงเซ โเชคเชฎเชพเชฐเซ เชเชฆเชฐเซเชถ เชเชฐเชฟเชฏเชฐ เชชเชพเชฅ เชถเซเชงเซ
2,521 เชเชพเชฐเชเชฟเชฐเซเชฆเซเชเชฎเชพเช เชเซเชถเชฒเซเชฏ-เชเชงเชพเชฐเชฟเชค เชฎเซเชเชฟเชเช. เชฎเชซเชค.
เชเชฐเชฟเชฏเชฐ เชฎเซเช เชเซเชธเซเช เชเชชเซ โ เชฎเชซเชค โ