Created
October 24, 2014 01:21
-
-
Save chrisfosterelli/bca847e8fc79816e7f3a to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WORKSHOP 2 | |
========== | |
Welcome! | |
You're going to do some software development now! | |
1. Create a Github account | |
2. Follow me on Github (https://github.com/chrisfosterelli) | |
3. Go to the gittalk2 demo repository | |
4. Fork the repository to your own account | |
5. Checkout your forked repository | |
6. Create a new branch and go to it | |
7. Add your name student number in a new file to the people directory | |
8. Commit that new file | |
9. Push that branch to your forked repository | |
10. Go to your forked repository on Github | |
11. Create a pull request with your changes | |
BONUS POINTS: | |
The code in that repository doesn't actually work. Can you fix it? | |
Only one person will be able to fix the code! Because as soon as I | |
merge into my repository then that becomes the "current" version. | |
BONUS POINTS 2: | |
Add some random functionality, or anything else you feel like, to | |
the repository's program. We are going to have 15 people at once editing | |
this code, so we might as well have some fun with it! | |
BONUS POINTS 3: | |
You are now out of date! Changes are getting merged into my repository, | |
but your forked repository is now out of date. To get everyone elses | |
commits, you have to do the following: | |
1. Add my "upstream" repository as a Git remote (google for how to do this) | |
2. Pull from my "upstream" repository | |
3. Push to your forked repository | |
And everything will be up to date! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment