>Everyone at work is using Git branches>I copy/paste files from git directory like retard>I am able to use only GitHub Desktop>I am fraud>Try to learn GIT on some random website>"Introduction" Level 1>Instruction: type git commit 2 times>I fucking broke it... how ?
>>107802497If only there was a way to interact with computers simply by using natural language.
>>107802497DID YOU REDEEM IT SIR?
just let ai agent do it lol
git pullgit add [file]git commitgit pushhow do you fuck this up?
>>107802497it's called RTFMhttps://git-scm.com/book/en/v2
>>107802497N
I don't understand what checkout does. How is this any different from git branch? Non tech fag I just use git for my personal projects
>>107802573checkout changes the working directory to match whatever's in a specific commit, not just the commit pointed to by a branch name.
>>107802573git branch creates the branchgit checkout -b creates the branch and switches to itgit checkout switches to an existing branchhonestly git checkout -b is usually what you want, i never use git branch
>>107802497Git was made by the same loser that made Linux and it's just about as user friendly. Anon here's my advice:1. Learn how git works: all you need to know is that a commit is a snapshot of all your files. Everything else: all the bad design and stupid commands and knowing how to get out of trouble flows from there. 2. Don't use git command line. Like all command line tools it's a waste of your time. You can use git-gui or better yet use a Jetbrains IDE and let it be your git interface.3. Don't waste your time organizing commit history: nobody reads it and people who say they do are lying. All these "learn git" games do is walk through convoluted ways to rearrange commits which is completely useless. All you ever need to do is:- create a branch- get the code on that branch to be what you want it to beWhen you ran> git checkout C1git did a retarded thing and detatched you from the `main` branch. So when you ran> git commityou created a new commit, but the `main` branch didn't update to point to the new commit. That's what > detatched HEAD statewas trying to say.What you could have done, after creating C3, is run> git branch -f mainto point the main branch at C3> git checkout mainto reattach `HEAD` to `main`.Or just don't check out a commit to begin with.But the real answer is to just not use the command line because it's a waste of your time.
I "learn" git GUI at workI know how to: add file before commit, commit, push, pull, reset to some history, switchafter few months I learned to make branch
>>107802497magit