- GitHub.com copy of the repo (central)
- Clone (initial acquisition)
- Make changes locally on laptop
- Push changes back to GitHub.com
- Pull to get any new central (GitHub.com) changes
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
An idea prompted by Jeremy Deane via a Tweet
> curl https://api.github.com/legacy/repos/search/Go?language=Go
{
"repositories": [
{
"type": "repo",
"username": "mattn",
"name": "go-gtk",
"owner": "mattn",
Hi I'm Matthew McCullough. I'm at @matthewmccull on Twitter. I work at GitHub as a trainer and need to organize lots of information in order to write books like Presentation Patterns, the O'Reilly Git book, Gradle book, and over a thousand presentations.
Today's big ideas are:
Delivered by Matthew McCullough on 2012-10-25
Thanks for attending the talk!
git clone https://github.com/matthewmccullough/training-repo-09-12.git mytrainingrepo
cd mytrainingrepo
echo CHANGE >> caesar.txt
git add caesar.txt
git commit -m "Changes"
git push
git branch matthewmccfeature
git checkout matthewmccfeature
vim matthewmcc.txt