Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
training:github_asynchronous_workflow [2016/05/15 19:04] kluong |
training:github_asynchronous_workflow [2021/09/19 21:59] (current) |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| - Figure out what you want to work on | - Figure out what you want to work on | ||
| - | - Create a new branch for your work | + | - Create a new branch for your work - name the branch with something descriptive. |
| - | - Do some work | + | - Ex. "add-user-page" |
| - | - Push up your branch when you're finished working on it for the day | + | - Do some work. Take a break, do some more work. |
| + | - Push up your branch up regularly, and make sure you push up when you're done working for the day | ||
| - Go to the repository in GitHub and submit a pull request for that branch | - Go to the repository in GitHub and submit a pull request for that branch | ||
| - Name it with that feature that you're working on | - Name it with that feature that you're working on | ||
| Line 35: | Line 36: | ||
| In general, this workflow allows us to work on features during our own time without having to meet together all the time. It's still good to meet together for some features, but the smaller ones can now be handled easier online. If you have any questions you can tag someone directly on the pull request and they can reply there. | In general, this workflow allows us to work on features during our own time without having to meet together all the time. It's still good to meet together for some features, but the smaller ones can now be handled easier online. If you have any questions you can tag someone directly on the pull request and they can reply there. | ||
| + | **Examples** | ||
| + | These closed pull requests provide some good insight to how the workflow can work: | ||
| + | |||
| + | * https://github.com/scel-hawaii/scel-hawaii.org/pull/19 | ||