View Code? Open in Web Editor
NEW
This project forked from baker-marlena/github-workflow-lesson
HTML 53.85%
JavaScript 9.31%
CSS 36.85%
github-workflow-lesson's Introduction
- Make sure that both partners have the ability to push directly to your main repository.
- All changes are pushed to Master directly.
- The partner who owns the repository does not give their partner any permissions for the repository.
- To work on the code, their partner must fork and clone the repository.
- When their partner wants to push changes to Github they must push the changes to their forked repository and submit a pull request.
- The partner who owns the repository must accept the pull request to have the changed merged into the master repository.
- Make sure that both parters have the ability to push directly to your main repository.
- For each task create a well named feature branch to commit your changes.
- When the changes are done and working the branch is merged into master.
- Make sure that both partners have the ability to push directly to your main repository.
- For each change create a well named feature branch to commit your changes.
- Push your branch to the remote repository and then make a pull request to have it merged in.
- Your partner should be the one to merge the pull request.
github-workflow-lesson's People
Watchers