Anonymous user
Open Source Comes to Campus/Github pull steps: Difference between revisions
Open Source Comes to Campus/Github pull steps (view source)
Revision as of 01:20, 25 September 2013
, 10 years agono edit summary
imported>Paulproteus (Created page with "== To fork a project on Github == * Start out logged in to Github * Visit the project you want to fork * Click the "Fork" button in the top-right * Wait for the animation ...") |
imported>Paulproteus No edit summary |
||
Line 1:
== Visiting the project on the web ==
Since this project is a website, we've specially configured the repository so that whenever there is a push to it, it is made visible on the web.
If your group's repository is called e.g. ''waffle-castle.github.io'', then you can see that the shared version is visible on the web at http://waffle-castle.github.io/.
But note that any changes in your ''fork'' won't show up there until the maintainer of the project merges those changes in.
== To fork a project on Github ==
Line 61 ⟶ 69:
Now, get feedback from the project's maintainer, and eagerly await your pull request getting merged!
== Once merged, visit your changes on the web ==
When your changes are merged into the main project repository, our specially configured repository will update the group website with the merged files.
This is a special trick that we do during the Git-based website editing project, using Github Pages. It demonstrates that when the merge happens, it can programmatically cause a different event; this is often called ''hooks''.
| |||