I don't know the git cli (well, not some of it)
#mostEmbarassingConfessions

Week 67? You see the future!?

@itsdaniel0 if this turns out to be right…

Just to mess with you I would make that the wk68. :D

@calmyourtities me too!
And cli isnt working in my computer, so it is a fine excuse

@calmyourtities I wouldn't worry too much though. I'm certainly not advanced in command line git. I can commit, merge, switch branches. That's about all I need to do :)

@itsdaniel0 @CozyPlanes I guess I'm not alone, except I'm the only one who posted wk67. Oh wait! @linuxer4fun did, but it was a typo

You don't have to know it. Just know a few commands you use commonly. If something breaks just copy it somewhere else and download it again. Also don't take my advice.

@calmyourtities xD

git status
git add -A
git commit
git push

You have seen everything.

Add git pull and selective git add filename and that's about all you need to know. Maybe git reset as well

I know git cli fairly well out of necessity. There is no GUI client that can do everything.
Even simple operations like making orphan branches, squashing history, replaying history on top of an orphan branch, merging two remotes, etc are too hard for GUI.
Not to mention stupid way they all handle recursively pulling submodules (usually wrong order) where they Bork on a conflict).

Also they never have a clear concept of local vs remote. If I have local changes I want to rebase. If I have server changes, I want to merge.

@nikolatesla save you some time:
git commit -am "stuff happened"
git push

a really easy to use git gui is www.gitkraken.com

@hitchhiker42 Stash is useful too. Also partially adding a file (selecting individual chunks) using add --patch.