lucy-musicalfish / CodingForDucks

ENGR101 Project 3 Team 23
0 stars 0 forks source link

Commits on Branches #9

Open lucy-musicalfish opened 4 years ago

lucy-musicalfish commented 4 years ago

Please make sure you are not committing anything to the main branch. The readme file should not be edited (on main or on anything else) by anyone except myself. I will update the versions section myself on the readme, so don't worry about updating that when you make a new branch. Make sure you make a new issue, so that I know which version number. If you are working on some code, here are some steps to keep the commits up: 1: Copy/paste the most recent version number of code into your own geany (easiest way is to keep a Robot.cpp file on your own computer, and when you want to work on a new version, delete everything in your robot.cpp, and replace it with what you have copied off latest version) 2: As soon as you have put your Robot.cpp on your computer, reupload it as a new branch, and make the initial pull request detailing your intentions. 3: Make the changes you wish to make, and reupload robot.cpp (regardless of how much you have changed whilst working on it) every 45-60 minutes, and commit your changes to your branch that you made in step 2. 4: only work on changing one aspect of the program per commit. Do not make a new branch every time you commit in step 3, just reupload and commit over your previous robot.cpp file in your branch.
5: Confused? I will explain this further in todays meeting.

Liam794 commented 4 years ago

this is valuable and helpful information!