The following guide set some guidelines to contribute with Sidekiq-Scheduler, please read it before start contributing.
- Make an individual pull request / issue for each suggestion / bug
- Search previous pull requests / issues before making a new one, as yours may be a duplicate
- Check your spelling and grammar
- Create an issue and use the
bug
label along with a brief description of the bug - Add a step-by-step guide to reproduce it along with the crash stacktrace
- Create an issue and use the
feature
label along with a brief description of the requested feature - Add a description explaining how to handle special cases
- Before creating a PR, create an issue related to what you are fixing / improving
- Add a brief description and a link to the related issue
- Follow our Commit Message Style Guide
- Use a correct branch-naming:
- For features use:
feature/add-support-for...
- For bug fixes use:
fix/handle-corner-case-...
- For features use:
- Make sure tests pass