--- title: "#version-control articles | Hashnode" description: "Explore 2,178 articles tagged #version-control on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/version-control" --- Tag # #version-control 2,178 posts · 117 followers [Amaresh Pelleti](https://hashnode.com/@amareswer) · [1d ago](https://hashnode.com/posts/git-recover-lost-commits-12-fixes-for-common-mistakes/6af7160c63c66a538700c037) ### [Git Recover Lost Commits: 12 Fixes for Common Mistakes](https://devtoolhub.hashnode.dev/git-recover-lost-commits-12-fixes-for-common-mistakes?utm_source=hashnode&utm_medium=feed) 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 . Almost every local Git 8 min read · [devtoolhub.hashnode.dev](https://devtoolhub.hashnode.dev/git-recover-lost-commits-12-fixes-for-common-mistakes?utm_source=hashnode&utm_medium=feed) [Min SiThu](https://hashnode.com/@itsmeminsithu) · [3d ago](https://hashnode.com/posts/how-does-merging-code-actually-work-branches-conflicts-and-pull-requests/6af5179500ec84dbbcd30bf4) ### [How Does Merging Code Actually Work? Branches, Conflicts, and Pull Requests](https://itsmeminsithu.hashnode.dev/how-does-merging-code-actually-work-branches-conflicts-and-pull-requests?utm_source=hashnode&utm_medium=feed) Two people changed the same file — here is what happens next, and why it is not scary 6 min read · [itsmeminsithu.hashnode.dev](https://itsmeminsithu.hashnode.dev/how-does-merging-code-actually-work-branches-conflicts-and-pull-requests?utm_source=hashnode&utm_medium=feed) [Abdus Salam](https://hashnode.com/@aheadkit) · [4d ago](https://hashnode.com/posts/git-stash-leaves-your-untracked-files-exactly-where-they-were/6af40b243f648bea981f71f5) ### [git stash Leaves Your Untracked Files Exactly Where They Were](https://aheadkit.hashnode.dev/git-stash-leaves-your-untracked-files-exactly-where-they-were?utm_source=hashnode&utm_medium=feed) 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 read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/git-stash-leaves-your-untracked-files-exactly-where-they-were?utm_source=hashnode&utm_medium=feed) [Atul Vishwakarma](https://hashnode.com/@vatul16) · [5d ago](https://hashnode.com/posts/gitlab-flow-guide/6af28d0fbc81d549b1f0fbc5) ### [GitLab Flow: The Middle Ground Between GitFlow and GitHub Flow](https://atulcodes.hashnode.dev/gitlab-flow-guide?utm_source=hashnode&utm_medium=feed) Environment branches, release branches, or a production branch: how to pick the GitLab Flow variant that matches the way you deploy. 6 min read · [atulcodes.hashnode.dev](https://atulcodes.hashnode.dev/gitlab-flow-guide?utm_source=hashnode&utm_medium=feed) [Min SiThu](https://hashnode.com/@itsmeminsithu) · [Nov 6](https://hashnode.com/posts/version-control-explained-simply-a-time-machine-for-your-code/6aedef8a948a6bd55e44613a) ### [Version Control, Explained Simply: A Time Machine for Your Code](https://itsmeminsithu.hashnode.dev/version-control-explained-simply-a-time-machine-for-your-code?utm_source=hashnode&utm_medium=feed) What Git actually does, why every team uses it, and the handful of ideas underneath the commands 6 min read · [itsmeminsithu.hashnode.dev](https://itsmeminsithu.hashnode.dev/version-control-explained-simply-a-time-machine-for-your-code?utm_source=hashnode&utm_medium=feed) [Amaresh Pelleti](https://hashnode.com/@amareswer) · [Nov 6](https://hashnode.com/posts/git-pull-vs-fetch-what-each-command-really-does/6aedda016d0f7c6ce5ac7fdc) ### [Git Pull vs Fetch: What Each Command Really Does](https://devtoolhub.hashnode.dev/git-pull-vs-fetch-what-each-command-really-does?utm_source=hashnode&utm_medium=feed) 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 read · [devtoolhub.hashnode.dev](https://devtoolhub.hashnode.dev/git-pull-vs-fetch-what-each-command-really-does?utm_source=hashnode&utm_medium=feed) [Amaresh Pelleti](https://hashnode.com/@amareswer) · [Oct 28](https://hashnode.com/posts/git-reset-vs-revert-vs-restore-which-to-use/6ae1f15db27ef2f6bbdfed8e) ### [Git Reset vs Revert vs Restore: Which to Use](https://devtoolhub.hashnode.dev/git-reset-vs-revert-vs-restore-which-to-use?utm_source=hashnode&utm_medium=feed) 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 read · [devtoolhub.hashnode.dev](https://devtoolhub.hashnode.dev/git-reset-vs-revert-vs-restore-which-to-use?utm_source=hashnode&utm_medium=feed) [Atul Vishwakarma](https://hashnode.com/@vatul16) · [Oct 27](https://hashnode.com/posts/gitflow-workflow-guide/6ae00f7d1e22047b4cea9996) ### [GitFlow Workflow: The Traditional Branching Model, and When It Still Makes Sense](https://atulcodes.hashnode.dev/gitflow-workflow-guide?utm_source=hashnode&utm_medium=feed) A practical guide to main, develop, release and hotfix branches, with commands, diagrams, and the mistakes that trip teams up. 5 min read · [atulcodes.hashnode.dev](https://atulcodes.hashnode.dev/gitflow-workflow-guide?utm_source=hashnode&utm_medium=feed) [6](https://hashnode.com/posts/gitflow-workflow-guide/6ae00f7d1e22047b4cea9996) [Waqas Shahid](https://hashnode.com/@practicaldevblog) · [Oct 26](https://hashnode.com/posts/git-branching-explained-work-without-breaking-the-main-code/6adf7cd9e98df8f19a1bdf81) ### [Git Branching Explained: Work Without Breaking the Main Code](https://practicaldevblog.hashnode.dev/git-branching-explained-work-without-breaking-the-main-code?utm_source=hashnode&utm_medium=feed) 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 read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/git-branching-explained-work-without-breaking-the-main-code?utm_source=hashnode&utm_medium=feed) [Alicia Drapeau](https://hashnode.com/@aliciadrap) · [Oct 20](https://hashnode.com/posts/getting-started-with-github-a-beginner-s-guide-to-repositories-and-commits/6ad6ea7c234a539addbdc55b) ### [Getting Started with GitHub: A Beginner's Guide to Repositories and Commits](https://aliciadrapeau.hashnode.dev/getting-started-with-github-a-beginner-s-guide-to-repositories-and-commits?utm_source=hashnode&utm_medium=feed) Learn how to create a GitHub repository, edit a README file, make commits, and review changes using GitHub's website. A simple guide for beginners. 7 min read · [aliciadrapeau.hashnode.dev](https://aliciadrapeau.hashnode.dev/getting-started-with-github-a-beginner-s-guide-to-repositories-and-commits?utm_source=hashnode&utm_medium=feed)