DEV Community

Git Commands ( to ease your development 🤗 )

Shivam on June 23, 2022

Git is a prevalent version control system ( VCS ) used by most programmers. In this blog, I am going to share some tips with basic commands to make...

Read full post

Asanka • Jun 23 '22

Good summary for useful basic git commands.

git stash pop only retrieves the first item (stash@{0}) from the stash list and then the index is refreshed (stash@{1} if it was there becomes the stash@{0} to take the place of the one popped out)

Shivam • Jun 23 '22

Thanks for correction, done updating. 👊

protium • Jun 26 '22 • Edited

Aliases are also totally needed for productivity 💪🏼. Theses are the ones I use the most:

# checkout or create new branch
ck = "!f() { git checkout $1 2>/dev/null || git checkout -b $1; }; f"

sync = !git pull origin main --rebase
up = !git push -u origin `git branch --show-current`

main = checkout main

Ritam Chakraborty • Jun 23 '22

git commit -am "Your commit message"

Changed my life. Read more about it here

stackoverflow.com/questions/429896...

Shivam • Jun 25 '22

Added ✌️

Zafer Gurel • Jun 24 '22 • Edited

If you're working with a remote repository and want to see the location of this remote repo, the following command might be helpful:

git remote -v

In addition to that, tagging is also a crucial feature of git. So, git tag command is also worth exploring.

Erik Garces Matos • Jun 25 '22

Good summary,

A tip:
We also can to put untracked files in stash, like this:

git stash --include-untracked

or

git stash -u

Shivam • Jun 25 '22

Sure I will be adding it soon. Thanks for suggestion

Nathan Stevenson • Jun 29 '22 • Edited

Let me introduce you to git reflog!

While git log shows us the repository's public commit history, git reflog (or git reference log) shows us our workplace-specific local commit history.

I'll tell you why this is important.

Ever accidentally mess up a rebase and lose everything in the last few commits? You check you log and there's no trace of the last several hours worth of work to be found? Oops

With reflog, no problemo. It will shown you those commits you thought were gonezo. Run the command, identify the latest commit, make note of the branch tip and run:

git reset --hard my-branch-tip-before-rebase

A sanity saver, for sure. Learned from experiencing my own moment of panic.