git-access is open source and contributions from the community are encouraged! No contribution is too small.
Please consider:
- adding a feature
- squashing a bug
- writing documentation
- reporting an issue
- fixing a typo
For the best chance of having your changes merged, please:
- Fork the project.
- Write a failing test.
- Commit changes that fix the tests.
- Submit a pull request.
- Be patient.
If your proposed changes only affect documentation, include the following on a new line in each of your commit messages:
[ci skip]
This will signal Travis that running the test suite is not necessary for these changes.
If you are experiencing unexpected behavior and, after having read git-access's documentation, are convinced this behavior is a bug, please:
- Search existing issues.
- Collect enough information to reproduce the issue:
- git-access version
- Specific setup conditions
- Description of expected behavior
- Description of actual behavior
- Submit an issue.
- Be patient.