matthewcunningham
commented
10 years ago Read.
Matthew
On Sun, Oct 27, 2013 at 8:54 PM, geppettodivacin notifications@github.comwrote:
@halfoff https://github.com/halfoff, @1turtleshttps://github.com/1turtles, @matthewcunningham https://github.com/matthewcunningham, @CallMePicklehttps://github.com/CallMePickle,
Everyone, we've completed Part 1 of this project! You can sync your master branch and try it out if you want. Also, I found a Kirby image (to go with the background) as an alternative to @CallMePicklehttps://github.com/CallMePickle's Nicolas Cage. It's on the "kirby" branch. I'd appreciate feedback for which ball sprite to go with.
Don't forget that you'll all have jobs for the second part, too. Make sure to check whichever email you've linked to GitHub, because I'll be sending your assignments through issues again. They'll work a little bit differently, though, and so I'll give you directions here. Please read them all the way through.
I will make a branch for you and tell you which branch to use. You will checkout the branch which I've made for you and edit the code there. DO NOT merge your branch with master at any time during the process of editing your branch. When you are done, send me a pull request and I'll merge it in. This will reduce confusion with messed up syncing.
During the process of editing your branch, be sure to commit any time you do something meaningful. If you aren't sure how much is meaningful, look at my commits. Typically any logically grouped set of changes should go in a commit. Some of your assignments will only require one commit, but you may want to have more in case you mess something up bad and want to go back.
In short, commit often, and let me worry about merging them all together at the end.
If you have problems with your code (not with the process of submitting them), send a pull request with a message that you need help. That way I'll be able to see the code with your message and be able to help you better.
Sorry this was so long. Please reply to this message if you read all the way through to let me know you've read it.
— Reply to this email directly or view it on GitHubhttps://github.com/TurtleTheater/Cannonball/issues/13 .
CallMePickle
geppettodivacin
halfoff
@halfoff, @1turtles, @matthewcunningham, @CallMePickle,
Everyone, we've completed Part 1 of this project! You can sync your master branch and try it out if you want. Also, I found a Kirby image (to go with the background) as an alternative to @CallMePickle's Nicolas Cage. It's on the "kirby" branch. I'd appreciate feedback for which ball sprite to go with.
Don't forget that you'll all have jobs for the second part, too. Make sure to check whichever email you've linked to GitHub, because I'll be sending your assignments through issues again. They'll work a little bit differently, though, and so I'll give you directions here. Please read them all the way through.
I will make a branch for you and tell you which branch to use. You will checkout the branch which I've made for you and edit the code there. DO NOT merge your branch with master at any time during the process of editing your branch. When you are done, send me a pull request and I'll merge it in. This will reduce confusion with messed up syncing.
During the process of editing your branch, be sure to commit any time you do something meaningful. If you aren't sure how much is meaningful, look at my commits. Typically any logically grouped set of changes should go in a commit. Some of your assignments will only require one commit, but you may want to have more in case you mess something up bad and want to go back.
In short, commit often, and let me worry about merging them all together at the end.
If you have problems with your code (not with the process of submitting them), send a pull request with a message that you need help. That way I'll be able to see the code with your message and be able to help you better.
Sorry this was so long. Please reply to this message if you read all the way through to let me know you've read it.