git init project2
cd project2
git status
mate index.html
git status
<body>
<p>First paragraph</p>
<p>First paragraph</p>
<p>Second paragraph</p>
<p>Second paragraph</p>
<p>Thirda paragraph</p>
<p>Thirdb paragraph</p>
</body>
git config --global core.editor "theprogramhere"
The editor should already be on your path such that you can run it by just typing its name at the prompt.
Notepad++ help can be found here
git diff
git diff --staged
git diff HEAD
git add -p
# answer s for split, y for yes, n for no
git log --author=Matt
git log -3
git log --stat
git log -p
git reset --hard
http://permalink.gmane.org/gmane.comp.version-control.git/217
- I have to take what I already know of github (a fair working knowledge plus today's course) back to a team of 4-5 devs (2 remote)
- They don't know github
- I have to convince them why they should bother learning github
- Be able to teach them enough so that we can all use it to work on our source code.
- The one question I know I'm going to get the most is if we all have our own cloned versions of a private github repo, how does one developer know what the other devs are working on?
- What are the best practices for handling that especially for binary files like Flash FLAs?
-
Can you reset an individual file?
git checkout HEAD -- <FILENAMEORPATHNAME> git checkout -- pageuno.html git checkout HEAD -- pageuno.html
git clone https://githubstudents:students987@github.com/githubstudents/hellogitworld.git
cd hellogitworld
git branch yournamegoeshere
git checkout yournamegoeshere
<create a new file called yournamegoeshere.txt>
git add yournamegoeshere.txt
git commit -m"message here"
git push -u origin yournamegoeshere:yournamegoeshere
git remote add matthewongithub https://github.com/matthewmccullough/hellogitworld
# Short form
git checkout feature_image
# Long form (if short is ambiguous)
git checkout -b feature_image --track origin/feature_image
git log --pretty=oneline master origin/master
https://github.com/robbyrussell/oh-my-zsh With the gozilla theme.