Feedback, bug reports, and pull requests are greatly appreciated :)
The following are all great reasons to submit an issue:
- You found a bug in the code.
- Something is missing from the documentation or the existing documentation is unclear.
- You have an idea for a new feature.
If you are thinking about submitting an issue please remember to:
- Describe the issue in detail.
- If applicable, describe the steps to reproduce the error, which probably should include some example code.
- Mention details about your platform: OS, version of Go and Redis, etc.
Jobs uses semantic versioning and the git branching model described here. If you plan on submitting a pull request, you should:
- Fork the repository.
- Create a new "feature branch" off of develop (not master) with a descriptive name (e.g. fix-database-error).
- Make your changes in the feature branch.
- Run the tests to make sure that they still pass. Updated the tests if needed.
- Submit a pull request to merge your feature branch into the develop branch. Please do not request to merge directly into master.