We're gonna break some stuff, and have fun all the while.
This section is begging for a merge conflict. So lets do it. (see "pull requests" below)
- Josh Thompson
- your name here
Here's how we'll spend some time:
- repos. name them silly things.
- remotes. Name them silly things.
- change remote URLs, name them sillier things
- branches. (make them dumb)
- add and committing
- delete our master branch, because why not?
- make a pull request.(this might inspire the aformentioned merge conflict) (oh, and re-add our master branch)
- check out earlier commit, branch from it. AKA kill your babies.
- Clean up. don't enter commands without understanding them.
Make a new repo inside of Github.com with a sorta awkward name. Perhaps because_josh_said_so or something like that.
mkdir a new folder on your computer for it to live in. Please know that you'll delete this folder at the end of today.
cd into that folder, and git init.
run git remote add origin <your_url>
make a file, save it, add it, and commit it. Once there's a file in the directory, git might behave more predictably.
curl turing.io -o turing.html will give you something to work with.
next, run git remote add smelly_socks <your_url>
run git remote -v
now do git remote add sooper_smelly_socks <your_url>
WTF, right?
LMK when you've done this.
lets clean up a bit. Run git remote -v. ugly and smelly, so clean that isht up:
git remote rm smelly_socks
git remote rm sooper_smelly_socks
git remote rm origin
Are you seeing a pattern? "git remote" isn't anything special. It's just telling git "whatever comes next is related to remote things"
and whatever comes after "git remote" is just telling git what to do.
yo git, add something that I'm gonna call "smelly_socks", and here's the URL for that: git@github.com:josh-works/git_practice.git
Now, when you say "smelly socks", git knows what URL you're talking about.
OK, more. re-add your origin URL, but don't call it origin. call it <yourname_origin>
so, I'd say:
git remote add josh_origin git@github.com:josh-works/git_practice.git
run git remote -v to make sure everything is as expected.
Cool. Now, go to your git repo, and change its name (somewhere in "settings"). It'll change the URL. Knowing what we have now worked through above, can you fix your now-broken remote URL?
(hint: besides just adding and removing remotes with git remote rm/add, there's also a git remote set-url that takes two arguments. )
Obviously we've seen repos called "origin", or "upstream", or other things like that. There's git conventions for naming repos and branches, just like there's ruby conventions that you shouldn't make MyCamelCaseVariable. So, make sure to use good names usually. But by now you should know what "origin" means in git push origin master.
run git branch
what branches do you see?
Probably just one. do git checkout holy_snaps_its_a_branch. what happens?
Probably some sort of error. turns out you need a -b flag when making a new branch.
try git checkout -b holy_snaps_its_a_branch. (Whoever reads this first - interrupt me and ask me about tab autocomplete for branches. Yeah, you. reading this right now... then go read this
run git branch again. Two branches, right? cool.
Make five more. I kid you not. Five more.
Once you have, take a screenshot of that part of your terminal, and post it to the #git_workflow channel in the turing slack.
delete those branches. Git will let you. If it doesn't, figure out why. Post to the #git_workflow the command you're using to delete a branch.
Deleted them? cool.
Make a new one. You're actually gonna change this one. That leads us to...
lets make some changes and see what happens there.
run curl http://ohshitgit.com/ -o ohshitgit.html
now cat ohshitgit.html
You front-enders should be all over this. To my untrained eye it looks like cryptic and mysterious ... html.
run git status. What do you see?
use the instructions to track them untracked files. but don't commit them yet.
run git status again. should be green, saying "stuff ready to be committed..."
commit it.
run git remote -v. If you have anything in there named origin, remove it. Make sure the only results in git remote -v is something crazy. here's mine:
now, open up your repo in your browser. Should look pretty bare.
back to the terminal:
git push funky_dance_moves master
suh-weet.
now, we did all this stuff on the master branch, which is a no no. So, do it again.
checkout a new branch. name it something... distinctive.
run curl http://www.nosweatshakespeare.com/resources/shakespeare-insults/ -o insults.html
if you copied and pasted that command, note the spelling error. fix it.
cat the file, take a peek. Cool, huh?
add and commit this stuff. check your repo online. do you see any of these changes?
prob not. back to the terminal:
do something exciting:
git br -d master
You just deleted your master branch. lolz. I'm writing and making this up as I go. It would be awkward if this wasn't fixable, huh?
git push <your_crazy_remote_name> <your_current_branch_name>
Here's what I entered:
git push funky_dance_moves new-branchy-branch
checkout your repo. anything interesting?
Your master branch might still be there. let's really delete it.
git branch -a => shows remote branches. (Think of -a as "all")
hm... I cannot figure out how to delete that branch from the command line.
you might be able to bring it back with git checkout master. try it.
Finish this out by creating a master branch again, checking it out, and using git merge <crazy_branch_name> master
Then delete all the non-master branches.
Fix your remotes too. rename your repo to origin, and delete the other name.
Ping the slack group when you're done.
CD out of your test git repo, and make another one that has the same name as the repo you're reading from right now.
OK. Fork this repo. Don't clone it, fork it. This will make a copy on your github profile. (Don't worry, you can delete it later)
Clone the forked repo from YOUR profile to the new folder you just made that has its same name.
use your adding remote skills to set it as your remote repo. something like
git remote add my_forked_copy <url_to_your_fork> will do it.
Now, add another remote pointing to MY copy!
you can use this string exactly, but type it in yourself:
git remote add joshs_repo git@github.com:josh-works/git_practice.git
run git remote -v and you'll see both. baller, right?
now, checkout a new branch. something like git checkout -b <myname_additions> will do fine.
cd into the put_stuff_here directory, read the readme, and follow the instructions.
now, once you're happy, push your branch to your forked copy of my repo, then open up my repo in the github ui. Submit a pull request.
open up my repo in the UI, and we'll walk through this pull request.
You should see something like this:
follow the instructions to create a pull request.
Let me know when you've done this. You're cruising.
By this point, you should be good with remotes and branching. That's kinda the bread-and-butter of your daily usage of git.
But, you'll want to make changes sometimes, or check out earlier versions of your project, right?
lets stage the project like this:
in this repo that you've forked, run git log. you'll get a long list of commits that I've made.
Find the earliest one, and copy the string of random numbers to your clipboard.
(protip - j or spacebar will move down the stuff printed to the screen. arrow keys might work too. hit q to exit it and get your terminal back.)
type git checkout 373aa65e13a7bfc2bc026efa49baf92d7e696dbd
you should see something like this:
zomg this is cool. now run git branch
You can see your current master and your old one. without changing anything, check each of them out a few times. run ls after each time. Do you see a change? Open up this markdown file in atom as you toggle between branches.
whoa.
run git diff master temp_old_branch. Should look crazy. don't stress about it.
hit q to escape.
OK, you've got to clean up your git profile, and your computer.
in the settings for the repo you made and the one you forked, delete them.
Then, CD into the directory one level above the directories we've been working in, and remove them. try rm <directory_name>. it won't work. In the #git_workflow slack channel, let us know what you're gonna enter to remove these directories, and explain both of the required flags.
Do not enter this command until you can explain exactly what each portion of the command does.
You're done! Good work. Hope it was helpful. If it wasn't, why are you still reading this? You've got better things to do with your life than sit listening to someone ramble on about something that's not useful to you. Go! Live your life!
To know what a terminal command means, use tldr. you'd then be able to type tldr rm and get something like this:
- What happens when you
git commitwith no-m? What is this hellscape you see? nbd: it's vim, and hit:q!to escape and try again. - eff. How do I un-f**k this... oh shit git
- Pretty terminal colors. What's up there? quick-and-dirty git autocomplete
- that wasn't enough terminal stuff. Give me more. here be dragons
- ACK I
git init'ed where I shouldn't have. ndb:rm -rf .git - Ack, I made changes on my
masterbranch! nbd:git stash,git co -b new_branch,git stash pop.