Git is one of the most widely used version control systems in modern software development. It allows developers to track changes, collaborate with teams, and manage project history efficiently. Whether you are a beginner or someone who wants to refresh their knowledge, understanding the basic Git commands is essential.<\/p>\n\n\n\n
In this article, we will go through the most commonly used Git commands with clear explanations and examples.<\/p>\n\n\n\n
Before making commits, Git needs to know who you are. This information will appear in your commit history.<\/p>\n\n\n
\ngit config --global user.name "Your Name"\ngit config --global user.email "your.email@example.com"\n<\/pre><\/div>\n\n\nTo check your current configuration:<\/p>\n\n\n
\ngit config --list\n<\/pre><\/div>\n\n\n
\n\n\n\n2. Navigating the Terminal<\/strong><\/h2>\n\n\n\nAlthough not Git-specific, these commands are commonly used while working with Git.<\/p>\n\n\n
\npwd\n<\/pre><\/div>\n\n\nDisplays the current directory.<\/p>\n\n\n
\nls # Displays the current directory\n<\/pre><\/div>\n\n\nLists files and folders in the current directory.<\/p>\n\n\n
\nls -a\n<\/pre><\/div>\n\n\nLists all files, including hidden ones such as .git<\/code>.<\/p>\n\n\n\n
\n\n\n\n3. Initializing a Git Repository<\/strong><\/h2>\n\n\n\nTo start using Git in a project, navigate to your project folder and run:<\/p>\n\n\n
\ngit init\n<\/pre><\/div>\n\n\nThis command creates a hidden .git<\/code> directory, which contains all the version control information for your project.<\/p>\n\n\n\n
\n\n\n\n4. Checking Repository Status<\/strong><\/h2>\n\n\n\nTo see the current state of your working directory:<\/p>\n\n\n
\ngit status\n<\/pre><\/div>\n\n\nThis command shows:<\/p>\n\n\n\n
\n- Modified files<\/li>\n\n\n\n
- Staged files<\/li>\n\n\n\n
- Untracked files<\/li>\n<\/ul>\n\n\n\n
It is one of the most frequently used Git commands.<\/p>\n\n\n\n
\n\n\n\n5. Adding Files to the Staging Area<\/strong><\/h2>\n\n\n\nTo add a specific file:<\/p>\n\n\n
\ngit add index.html\n<\/pre><\/div>\n\n\nTo add all files:<\/p>\n\n\n
\ngit add .\n<\/pre><\/div>\n\n\nThe staging area allows you to choose which changes will be included in the next commit.<\/p>\n\n\n\n
\n\n\n\n6. Committing Changes<\/strong><\/h2>\n\n\n\nOnce files are staged, you can save them to the repository with a commit:<\/p>\n\n\n
\ngit commit -m "Initial project setup"\n<\/pre><\/div>\n\n\nA commit message should be short, clear, and descriptive.<\/p>\n\n\n\n
\n\n\n\n7. Viewing Commit History<\/strong><\/h2>\n\n\n\nTo see the list of commits:<\/p>\n\n\n
\ngit log\n<\/pre><\/div>\n\n\nFor a compact view:<\/p>\n\n\n
\ngit log --oneline\n<\/pre><\/div>\n\n\nThis helps you understand the project\u2019s history and track changes over time.<\/p>\n\n\n\n
\n\n\n\n8. Viewing File Differences<\/strong><\/h2>\n\n\n\nTo see changes that are not staged yet:<\/p>\n\n\n
\ngit diff\n<\/pre><\/div>\n\n\nTo see changes that are staged:<\/p>\n\n\n
\ngit diff --staged\n<\/pre><\/div>\n\n\nThis command shows line-by-line differences between versions.<\/p>\n\n\n\n
\n\n\n\n9. Working with Branches<\/strong><\/h2>\n\n\n\nBranches allow you to work on features independently without affecting the main codebase.<\/p>\n\n\n\n
List branches:<\/p>\n\n\n
\ngit branch\n<\/pre><\/div>\n\n\nCreate a new branch:<\/p>\n\n\n
\ngit branch feature-login\n<\/pre><\/div>\n\n\nSwitch to a branch:<\/p>\n\n\n
\ngit switch feature-login\n<\/pre><\/div>\n\n\nOr using the older command:<\/p>\n\n\n
\ngit checkout feature-login\n<\/pre><\/div>\n\n\n
\n\n\n\n10. Merging Branches<\/strong><\/h2>\n\n\n\nTo merge a branch into the current branch:<\/p>\n\n\n
\ngit merge feature-login\n<\/pre><\/div>\n\n\nThis combines the changes from the selected branch into your active branch.<\/p>\n\n\n\n
\n\n\n\n11. Undoing Changes<\/strong><\/h2>\n\n\n\nRestore a modified file:<\/p>\n\n\n
\ngit restore index.html\n<\/pre><\/div>\n\n\nRemove a file from staging (but keep it locally):<\/p>\n\n\n
\ngit rm --cached index.html\n<\/pre><\/div>\n\n\n
\n\n\n\n12. Reverting a Commit<\/strong><\/h2>\n\n\n\nTo safely undo a commit without rewriting history:<\/p>\n\n\n
\ngit revert <commit-hash>\n<\/pre><\/div>\n\n\nThis creates a new commit that reverses the changes.<\/p>\n\n\n\n
\n\n\n\n13. Resetting Commits<\/strong><\/h2>\n\n\n\nGit reset allows you to undo commits in different ways:<\/p>\n\n\n
\ngit reset --soft HEAD~1\n<\/pre><\/div>\n\n\nKeeps changes staged.<\/p>\n\n\n
\ngit reset --mixed HEAD~1\n<\/pre><\/div>\n\n\nKeeps changes but unstages them.<\/p>\n\n\n
\ngit reset --hard HEAD~1\n<\/pre><\/div>\n\n\n\u26a0\ufe0f Completely removes changes (use with caution).<\/p>\n\n\n\n
\n\n\n\n14. Using .gitignore<\/code><\/strong><\/h2>\n\n\n\nTo prevent certain files from being tracked:<\/p>\n\n\n
\ntouch .gitignore\n<\/pre><\/div>\n\n\nExample .gitignore<\/code> content:<\/p>\n\n\n\nnode_modules\/\n.env\n*.log\n<\/pre><\/div>\n\n\nThis is especially useful for ignoring sensitive files or dependencies.<\/p>\n\n\n\n
\n\n\n\n15. Removing Git from a Project<\/strong><\/h2>\n\n\n\nTo completely remove Git tracking:<\/p>\n\n\n
\nrm -rf .git\n<\/pre><\/div>\n\n\nThis deletes all Git history from the project.<\/p>\n\n\n\n
\n\n\n\nConclusion<\/strong><\/h2>\n\n\n\nGit is an essential tool for every developer. By mastering these basic Git commands, you can manage your code efficiently, collaborate with others, and maintain a clean project history. As you grow more comfortable with Git, you can explore advanced features like rebasing, cherry-picking, and remote repositories.<\/p>\n\n\n\n
Happy coding \ud83d\ude80<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"