Contributing to GitNex
Please take a few minutes to read this document to make the process of contribution more easy and healthy for all involved.
Be polite and gentle while commenting or creating new issues to maintain a healthy environment in which everyone is able to feel comfortable.
Issues and Reports
Before creating an issue please take a moment and search the repository issues(open/closed) to avoid duplicate issues either it's a bug or feature.
In case you want to submit a bug report, please provide as much details as possible to better debug the problem. The important part is how to reproduce the bug and steps to reproduce are appreciated.
Note: Please contact the project directly via email if have to share sensitive and security related details.
Patches, enhancements and features are always welcome. The PR should focus on the scope of work and avoid many unnecessary commits. Please provide as much detail and context as possible to explain the work submitted.
Please ask if you are not sure about the scope of work to be submitted to avoid waste of time spent on the work. (Submit an issue, before submitting a PR)
Please follow the code standards, this will help other developers to understand your code too.
It also helps maintaining the code afterwards.
It is documented in the Wiki: Code-Standards
How to submit a PR (Pull Request)
- Fork this repository.
- Clone the forked repository from your namespace to your local machine.
- Create a new branch and work on your feature, enhancement or patch.
- Push your commits to your forked version.
- You can now create a PR using the web interface against main branch.
For more information, click here.
IMPORTANT: By submitting PR, you agree to allow GitNex to license your work under the same license as that used by GitNex.