Royce  Reinger

Royce Reinger

1628146800

Top 7 Git Commands You Might Not Know

Almost every software developer today knows at least a little bit about Git. In order to go beyond this "little bit", I'd like to show you seven short commands which you might not know - and which might help you become more productive and proficient with Git!

Using "git switch" Instead of "git checkout"

Switch Back to the Previous Branch

Undoing Local Changes with "git restore"

Making "git status" More Concise

Using the Reflog to Save Your Neck

Staging Parts of a File for the Next Commit

Saving Parts of a File on the Stash

#git 

What is GEEK

Buddha Community

Top 7 Git Commands You Might Not Know

7 Best Practices in GIT for Your Code Quality

There is no doubt that Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Still, developers struggle for code quality. Why? They fail to follow git best practices. In this post, I will explain seven core best practices of Git and a Bonus Section.

1. Atomic Commit

Committing something to Git means that you have changed your code and want to save these changes as a new trusted version.

Version control systems will not limit you in how you commit your code.

  • You can commit 1000 changes in one single commit.
  • Commit all the dll and other dependencies
  • Or you can check in broken code to your repository.

But is it good? Not quite.

Because you are compromising code quality, and it will take more time to review codeSo overall, team productivity will be reduced. The best practice is to make an atomic commit.

When you do an atomic commit, you’re committing only one change. It might be across multiple files, but it’s one single change.

2. Clarity About What You Can (& Can’t) Commit

Many developers make some changes, then commit, then push. And I have seen many repositories with unwanted files like dll, pdf, etc.

You can ask two questions to yourself, before check-in your code into the repository

  1. Are you suppose to check-in all these files?
  2. Are they part of your source code?

You can simply use the .gitignore file to avoid unwanted files in the repository. If you are working on more then one repo, it’s easy to use a global .gitignore file (without adding or pushing). And .gitignore file adds clarity and helps you to keep your code clean. What you can commit, and it will automatically ignore the unwanted files like autogenerated files like .dll and .class, etc.

#git basics #git command #git ignore #git best practices #git tutorial for beginners #git tutorials

Monty  Boehm

Monty Boehm

1620615985

Top 35 Git Commands With Examples

Git commands are essential, and they help to manage your source code effectively. In this guide, you will learn Git commands from Beginners to Advanced level.

If you are a new or experienced developer, you have to use source control. And good chances are you are using Git to manage your source code.

And to use Git to its full potential, you need to know Git commands. Here you will learn the most helpful Git commands that will take you from one level to another.

To make this Git commands guide more helpful, I have divided the guide into three different sections: Basic, Intermediate, and Advanced Git commands.

This is an epic guide. And to make it more useful, I have added a Bonus section where you can download  51+ Git commands and a few more downloads to boost your productivity in Git.

Basic Git Commands

In this section, you will learn the essential Git commands. These basic Git commands are the foundation to learn more advanced commands.

Here are the nine useful Git commands.

1. git config

2. git version

3. git init

4. git clone

5. git add

6. git commit

7. git status

8. git branch

9. git checkout

10. git remote

11. git push

13. git fetch

14. git pull

15. git stash

16. git log

17. git shortlog

18. git show

19. git rm

20. git merge

21. git rebase

22. git bisect

23. git cherry-pick

24. git archive

26. git blame

27. git tag

28. git verify-commit

29. git verify-tag

30. git diff

31. git citool

32. git mv

33. git clean

34. git help

35. git whatchanged

#git #git commands #git commits #git tutorial

Myriam  Rogahn

Myriam Rogahn

1593435300

Basic Git Commands you need to Master

In this part you will get familiar with some basic Git commands. At the end of this blog you will be able to perform certain task like

  • Set up a folder as a Git repository
  • Perform basic Git operations on your Git repository

These are those commands you must conquer

Basic Git Commands

  • At any location on your computer, create a folder named git-test.
  • Open this git-test folder in your favorite editor.
  • Add a file named index.html to this folder, and add the following HTML code to this file:
<!DOCTYPE html>

<html>
<head></head>
<body>
<h1>Sab Batade Aapko</h1>
</body>
</html>

Initializing the folder as a Git repository

  • Go to the git-test folder in your cmd window/terminal and type the following command at the prompt to initialize the folder as a Git repository:
git init

this command will make a file named .git

#github #git #basic-git-commands #git-commands #git-status

Rupert  Beatty

Rupert Beatty

1617875220

Git Commands You Can Use To Dig Through Your Git History

In this short article, we’ll be exploring some quick  git commands that can help us in digging through our repositories’ history of commits. We’ll look at

  1. git log
  2. git shortlog
  3. git show
  4. git rev-list

#git #git-log #git-commands #git-history #aws

Lenora  Hauck

Lenora Hauck

1591873860

7 Git Commands You May Not Know

GitHub recently went free for teams which is great news for all devs. We all have our everyday Git commands that we use over and over. But what if I told you there are some lesser known Git commands that may make your life easier. In this article, we are going to go over the top 7 lesser-know Git commands. Some of these you may have used, some may be new to you, and some you might think there’s no way this is going to work. 😳 But you’ll never know until you try them out!

#git #7 git commands