Tag

#version-control

2,178 posts117 followers

Explore Hashnode

Alternatives

Git Recover Lost Commits: 12 Fixes for Common Mistakes

Originally published on DevToolHub. To git recover lost commits, run git reflog, find the hash from before the mistake, and point a branch at it with git branch rescue <hash>. Almost every local Git

8 min readdevtoolhub.hashnode.dev

Min SiThu3d ago

How Does Merging Code Actually Work? Branches, Conflicts, and Pull Requests

Two people changed the same file — here is what happens next, and why it is not scary

6 min readitsmeminsithu.hashnode.dev

Abdus Salam4d ago

git stash Leaves Your Untracked Files Exactly Where They Were

I used to think git stash put my working tree back to a clean HEAD. That is wrong in a specific and painful way, and I found out on a day when I stashed my work to pull a teammate's branch, then watch

5 min readaheadkit.hashnode.dev

Atul Vishwakarma5d ago

GitLab Flow: The Middle Ground Between GitFlow and GitHub Flow

Environment branches, release branches, or a production branch: how to pick the GitLab Flow variant that matches the way you deploy.

6 min readatulcodes.hashnode.dev

Min SiThuNov 6

Version Control, Explained Simply: A Time Machine for Your Code

What Git actually does, why every team uses it, and the handful of ideas underneath the commands

6 min readitsmeminsithu.hashnode.dev

Amaresh PelletiNov 6

Git Pull vs Fetch: What Each Command Really Does

Originally published on DevToolHub. git fetch downloads new commits and leaves your branch and your files alone. git pull runs a fetch and then merges or rebases the result into your current branch.

9 min readdevtoolhub.hashnode.dev

Amaresh PelletiOct 28

Git Reset vs Revert vs Restore: Which to Use

Originally published on DevToolHub. Use git reset to move your branch back, git revert to undo a commit with a new commit, and git restore to fix files without touching history. The git reset vs reve

10 min readdevtoolhub.hashnode.dev

Atul VishwakarmaOct 27

GitFlow Workflow: The Traditional Branching Model, and When It Still Makes Sense

A practical guide to main, develop, release and hotfix branches, with commands, diagrams, and the mistakes that trip teams up.

5 min readatulcodes.hashnode.dev

6

Waqas ShahidOct 26

Git Branching Explained: Work Without Breaking the Main Code

Introduction A branch is a separate line of work in Git. The main branch, usually called main, holds the stable code. When you start a feature or a fix, you create a branch, work there, and merge it b

3 min readpracticaldevblog.hashnode.dev