i love to make git commits. i love to stage things and then push them. i love it
you: git is really complicated, what if i push the wrong thing
me, rotating five million branches in my head: augughuguaauuhuuuuuuuuu
"she got it in her"
the spirit is weak. woe be the spirit. the body is weaker still. Siërra R
.
ask me about horses
.
dreamwidth
botflymother.dreamwidth.org/website
botflymother.neocities.org/bandcamp
botflymother.bandcamp.com/soundcloud
soundcloud.com/botflymothersomewhere on website league
username will be botflymother
really if you wanna find me just look for botfly mother
gonna keep that name around for a good while
You must log in to comment.
in reply to @hthrflwrs's post:
i know only the most simplistic git commands and whenever someone tries to teach me more i unplug my computer.
someone once taught me git add -p and my brain has been irreparably broken (only ever commits singular, whole changes) ever since.
i know enough about git and how it works internally to be able to recover from most forms of screw-up and i cant tell if it's better or worse than not knowing that
My git recovery procedure is pretty air-tight:
If the code on your PC is wrong and the code on the server is correct, rm -rf your local project directory and pull a fresh copy.
If the code on your PC is correct and the code on the server is wrong, rename your local project directory, rm -rf .git, pull a fresh copy, delete everything but .git, copy everything over from the old project, and git add . to force it into sync.
Remember, kids: Always push after every commit, always pull before you start your work, and never use git commit -a because you already pushed the code and it won't push the amendment (which is something I learned the hard way multiple times).
Pinned Tags