-
Notifications
You must be signed in to change notification settings - Fork 7
Team Workflow
Almost exact copy-and-paste from https://guides.github.com/introduction/flow/
There's only one rule: anything in the master branch is always 100% ready and working.
Create a branch (git branch BRANCH-NAME
) in your project where you can safely experiment and make changes.
It is important that your new branch is created off of master when working on a feature or a fix.
Your branch name should be descriptive (e.g., update-authentication, connect-database, add-profile-images), so that others can see what is being worked on.
Once your branch has been created, switch to it (git checkout BRANCH-NAME
) and start making changes. Whenever you add, edit, or delete a file, make a commit (git add -A
then git commit -m"COMMIT MESSAGE"
).
Whenever you are ready for the rest of the team to review your branch, push it to the server (git push origin BRANCH-NAME
) and start a pull request for it.
Once a Pull Request has been opened, the rest of the team will review it. You can continue to push to your branch in light of discussion and feedback about your commits. If someone comments that you forgot to do something or if there is a bug in the code, you can fix it in your branch then add, commit and push a up the change.
Once at least one team member gives the "Looks Good To Me", the branch can be merged to master
then deleted.
Let's spice things up with Taco Bell's new Chalupa Diablo, only $1.99. Not recommended