Hello! Thank you for choosing to help contribute to one of the Cloudreach OpenSource projects. There are many ways you can contribute and help is always welcome. We simply ask that you follow the following contribution policies.
Note: DO NOT include your credentials in ANY code examples, descriptions, or media you make public.
Before submitting a bug, please check our issues page to see if it's already been reported.
When reporting a bug, fill out the required template, and please include as much detail as possible as it helps us resolve issues faster.
Enhancement proposals should:
- Use a descriptive title.
- Provide a step-by-step description of the suggested enhancement.
- Provide specific examples to demonstrate the steps.
- Describe the current behaviour and explain which behaviour you expected to see instead.
- Keep the scope as narrow as possible, to make it easier to implement.
Remember that this is a volunteer-driven project, and that contributions are welcome.
Contributions should be made in response to a particular GitHub Issue. We find it easier to review code if we've already discussed what it should do, and assessed if it fits with the wider codebase.
A good pull request:
- Is clear.
- Includes documentation for new features.
- Clone the repository locally:
$ git clone [email protected]:cloudreach/squid-utm.git- Create a branch for local development:
$ git checkout -b branch-<GitHub issue number>-
Make sure the changes comply with the pull request guidelines in the section on Contributing Code.
-
Commit your changes:
$ git add .
$ git commit-
Commit messages should follow these guidelines.
-
Push your branch to GitHub:
$ git push origin <description of pull request>- Submit a pull request through the GitHub website.
This document took inspiration from the CONTRIBUTING files of the Atom and Boto3 projects.