This document provides an overview on how to contribute to GMSVToolkit, and will provide step-by-step instructions on a practical contribution workflow.
- Make sure you have an active GitHub account
- Download and install git
- Read the git documentation
- Install the main branch of the SCECcode/gmsvtoolkit.git repository
- If you haven't worked with Git Forks before, make sure to read the documentation linked below.
Pull requests are great! Please submit them to us! Here's how:
- Fork the repo. Some helping info
- Make a new branch.
- Add a test! Only pull requests for documentation and refactoring do not require a test.
- Make sure the tests pass. Run
./UnitTests.shin the tests directory of the repo. - Push your changes to your fork and submit a pull request.
- Wait for our review. There may be some suggested changes or improvements. Changes can be made after the pull request has been opening by simply adding more commits to your branch.
Pull requests can be changed after they are opened, so create a pull request as early as possible. This allows us to provide feedback during development and to answer any questions.
Please make sure to set the correct branch for your pull request. Also, please do not include large files in your pull request. If you feel that you need to add large files, let us know and we can figure something out.
Please open an issue if you want to ask a question about the GMSVToolkit.
- Please search through the past issues to see if your question or the bug has already been addressed
- Please apply the correct tag to your issue so others can search
If you want to submit a bug report, please provide the information below:
- GMSVToolkit version, Python version, and Platform (Linux, Windows, Mac OSX, etc)
- How did you install the GMSVToolkit
- Please provide a short, complete, and correct example that demonstrates the issue.
- If this broke in a recent update, please tell us when it used to work.
- Working with Git Forks
- Style Guide
- Docs or it doesn’t exist
- Performance Tips: