Thanks for taking the time to contribute! Contributors are what make Climb Beta great and we are happy to have you here.
Please, read over our Contributing Guidelines and Code of Conduct.
View our issues to see where you can help. Choose an issue that you feel comfortable working on. When working on your selected issue, be sure to create a new feature/issue branch and fork the Climb Beta repository.
Working on an issue and ready to send a pull request? Go through this checklist to make sure it fits our guidelines.
- Read Contributing Guidelines
- Read Code of Conduct
- Rebase your changes. Make sure your local repository is updated with the most recent code from the Climb Beta Repository.
- Include tests where applicable
- Run app Unit Tests (including your own)
- Submit pull Request. Follow our pull request format.
| Title | Description |
|---|---|
| Issue Number and Title | Problem: Problem the pull request addresses Solution: What the pull request does to fix this problem Notes: Any additional notes that are necessary |
- Found a bug? Make sure it is not already reported in issues
- If not, open a new issue. Including the following:
- Short and descriptive title
- Clear description of the issue
- As much relevant information as possible. Try not to leave others looking for more information.
- Code Sample or Test Case to show an expected behavior that is not occurring.
Have an idea that could make Climb Beta better and more useful? When submitting a feature request make sure to do the following:
- Take a moment to think if your idea fits the scope and aim of Climb Beta.
- Make a strong case for your idea. Provide information about how and why your feature needs to be included in Climb Beta.
- Provide as much details and context as you can.