-
Notifications
You must be signed in to change notification settings - Fork 130
Contributing to NewSources
- Clone this repository to your own Github using the fork button at the top-right corner of the Github page. This will create a read-write repository for you. The main NewSources repo is read-only, so your own read-write copy will be your editing stage.
Clone the repository on your local machine using git commandline or Github for Windows/Mac.
- Using the shell, use git checkout -b my-feature
- Using Github for Mac or Windows, press the new-branch button.
Go forth and edit the files. Make the changes you'd want.
Use the command-line to commit or use Github for Windows/Mac. Some rules for orderly merges:
- Bundle changes into one commit.
- Make sure your commits are not too large. Merging your changes is easier if your changesets are small.
- Bundle multiple commits into one Pull Request.
For example when adding a Hunter class:
- Each ability could be one nice commit.
- Fixing mistakes could be another commit.
- Renaming everything should also be one commit.
- These commits together form a nice Pull Request with title "Add Hunter to ACG".
Go to your own Github page for your own NewSources repository. You'll see that you've recently pushed branches. Press the big green button and write a description for your changes. Please be verbose. It helps to review your changes. When you are done describing your changes, press "Create pull request".
So you're all done! Go back to step 3. to add a new feature.
After you've created a Pull Request, you will probably receive feedback from fellow developers. They might ask for fixes. Please fix these in the feature branch you created the PR from and add more commits. Just push to your repository to update the PR automatically.