Create templates to quickly answer FAQs or store snippets for re-use.
Good one! Once you go console and learn the basics you'll never look back.
Setting editor of choice
I remember a fright of ending up in 'vi'-mode for commit messages. If you, like me, couldn't care less of learning how to use the vi-editor properly you should set git to fire the editor of your choice.
git config --global core.editor "notepad"
notepad, vs code ("code"), sublime, atom etc.
It's a great article. Just one thought from my side since you follow the order of git add, git commit and then git push, I wanted to say this:
If we are working on a shared repository and two or more people are working on it. So it would be a good practice to pull the latest code from the master before pushing our local changes. So that we will always be in sync with other's pieces of code too.
Thank you for adding such a great point.
I rearranged the order multiple times. I actually had it in the order you suggest and then changed it again last minute. As this is a post geared more towards beginners, I figured I'd try to explain the most basic commands first then touch on the ones that are used when pair programming/working with others. I didn't want to make things too complicated. That's why I did the last 3 commands together, since they are all geared towards working with others and are a tad more involved.
Loved this guide for those who are newbs sing Git, awesome!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.