ProgrammerHumor
initialCommitViaCLIBeLike
Discussion
I love this gif
What's hard to remember about git push?
terminal scary
It’s all and great until you’re a few commits behind and merge conflicts happen…
I have several ideas why that might not work.
- You haven't added new files or have no tracked files. * You have tracked files, but you did not commit them.
- You have committed them, but remote is ahead, and your changes cause a conflict, which leads to a rejected push.
In all these cases git push won't help you, as a single command.
This why terminal scary
fatal: The current branch has no upstream branch
conflict merge
Sounds like you are working on a small project by yourself. When you are working on larger projects with multiple people you can't just git push by itself.
If you have the right permissions, you can use --force to get past a lot of issues with git.
git add .
git commit -m 'bug fix and stuff'
git push origin master --force
wow brb bro gonna go do this on one of the repos at my job
Also, don't forget the good ol' git branch -D main
GitHub desktop or VSCode built-in Git extension. Never had to write a command
i'm so lazy that once the CLI stopped working for me I just used the github website.
i did google the problem, though. i think i had to delete an old password from the keychain but i couldn't figure out how to do that. like i could literally see what to click on but i couldn't click it
People like terminal because they think it makes them look smart.
I never used and never will, there is a reason we moved from msdos to windows.
How else were we gonna play GTA 6?
Hahahaah good one
Not every computer has a gui, especially servers. Also not every ide has buttons for using git. So if you want to have version control on a remote server you need to use cli/terminal
If you are commiting from a server, I'm sorry,
There is GitHub desktop which is freem
Whoever is programming on a remote server, I'm sorry for you..
I program on a remote machine. It's fantastic and has literally hundreds of times better hardware than my laptop. I can WFH and literally program on a beach and have all the hardware I want and not step a foot in an office. It's all mostly done through ssh and CLI because remote desktop software is pretty slow and clunky.
You should try it it's great.
It's awesome but it's clunky ?
Remote desktop software is clunky. They're using SSH, which is a terminal-based remote access program.
Github desktop is not officially supported on linux, so unless you're using git exclusively on windows and Mac it's not an option. Maybe it's a strong opinion but the need for a gui application to have version control seems way too big of a crutch for me. As a programmer a basic understanding of the terminal is (at least in my experience and opinion) expected, the need to click through menus seems unnecessary and a waste of time compared to using the terminal. And git cli is universal, gui applications for git are not.
If you’re using Linux, you’re a command geek anyways
As a programmer, basic understanding of terminal is just bullshit. We just need to get thing done with the least effort.
Anything you add because you feel like you should use it know is just for your ego
I use terminal because it's the environment that is most comfortable and convenient to me. In a job, it's also very common to dev/deploy/test on remote servers, so that terminal might be your only choice.
Some people apparently have a fear of commitment. But seriously: learn the commands by using them!
VSCode UI does the important stuff for you
sourcetree
It's been a long time since I actually laughed out loud on this sub. Nice one!
I'm even worse than that guy. I use the tool in visual studio
I get why people are uncomfortable with it but it's like everything else. The more you use it the better you get with it. If you let yourself use one of the graphical apps to do git for you, you won't ever learn how to use the tool.
There are a ton of git clients out there. I used SourceTree when I started, and it eased me up into git since it also displays the commands it uses to fetch, checkout, create pull requests, prune, rebase, etc.
pwd git status git add —all git commit -m “I love git” git push git status
I want to share this at work, but probably not appropriate.
3 git command to remember.
Git add
Git commit
Git push
Everything else look up on the internet as they come up.
git rebase -i is the only command you'll need to know other than commit and push
git stash
git switch
git restore
...
git pull
rebase is dirty
Use this: https://education.github.com/git-cheat-sheet-education.pdf
He is. He said he had to use a cheat sheet every time.