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 19:06, 9 May 2014
, 10 years ago→To fork a project on Github
imported>Paulproteus No edit summary |
imported>Shauna |
||
| (11 intermediate revisions by the same user not shown) | |||
Line 17:
* Wait for the animation to conclude
* Notice that your browser is now visiting a copy of the project in your personal space, rather than the old, group-owned one. You should also see a "fork of..." remark in the top-left. (See [https://openhatch.org/wiki/File:Forks.png here] for screenshot.)
== Now, clone to it to your computer ==
Line 33:
* Once you've done that, "cd" into the directory.
==
* Open index.html in your favorite text editor -- it should look like a regular HTML page
Line 45:
== Find a task ==
Now, find a bug on the project's issue tracker that you will work on, and
(Before you do that, make sure to refresh the page and check that no one else has claimed it while you were reading and deciding.)
== Resolve the task ==
How you do this depends on the issue you've chosen. If you run into a problem you can't seem to solve, try asking the student next to you or one of the mentors.
Make sure to open up index.html and check that your solution works.
== Commit and push ==
Once you're finished making changes, you can use the following command to get a list of files you've changed:
git status
You can commit your changes by typing "git add" followed by the files you've changed, for instance:
git add index.html
Once you've added the changes, you can "commit" them with a message specifying what you've changed.
git commit -m "Explanation of my changes"
Line 61 ⟶ 73:
git push
== Create pull request ==
Now, get feedback from the project's maintainer
== Once merged, visit your changes on the web ==
| |||