|
| 1 | +# Contributing to capistrano-sidekiq |
| 2 | + |
| 3 | +We love pull requests from everyone. By participating in this project, you agree to abide by our code of conduct (coming soon). |
| 4 | + |
| 5 | +## Getting Started |
| 6 | + |
| 7 | +1. Fork the repository |
| 8 | +2. Clone your fork: `git clone [email protected]:your-username/capistrano-sidekiq.git` |
| 9 | +3. Set up your development environment: `bundle install` |
| 10 | +4. Create a feature branch: `git checkout -b my-new-feature` |
| 11 | + |
| 12 | +## Making Changes |
| 13 | + |
| 14 | +1. Make your changes |
| 15 | +2. Add tests for your changes |
| 16 | +3. Run the test suite: `bundle exec rake test` |
| 17 | +4. Update documentation if necessary |
| 18 | +5. Update CHANGELOG.md with your changes |
| 19 | + |
| 20 | +## Code Style |
| 21 | + |
| 22 | +- Follow Ruby community style guidelines |
| 23 | +- Keep code simple and readable |
| 24 | +- Add comments for complex logic |
| 25 | +- Use meaningful variable and method names |
| 26 | + |
| 27 | +## Testing |
| 28 | + |
| 29 | +- Write tests for any new functionality |
| 30 | +- Ensure all tests pass before submitting |
| 31 | +- Test with different Ruby versions if possible |
| 32 | +- Test with Docker: `bundle exec rake test` |
| 33 | + |
| 34 | +## Submitting Changes |
| 35 | + |
| 36 | +1. Push to your fork: `git push origin my-new-feature` |
| 37 | +2. Create a pull request |
| 38 | +3. Describe your changes in the PR description |
| 39 | +4. Reference any related issues |
| 40 | + |
| 41 | +## Pull Request Guidelines |
| 42 | + |
| 43 | +- Keep PRs focused on a single feature or fix |
| 44 | +- Update documentation for any changed behavior |
| 45 | +- Add entries to CHANGELOG.md |
| 46 | +- Ensure CI passes |
| 47 | +- Be responsive to feedback |
| 48 | + |
| 49 | +## Reporting Issues |
| 50 | + |
| 51 | +- Use the GitHub issue tracker |
| 52 | +- Check if the issue already exists |
| 53 | +- Include reproduction steps |
| 54 | +- Provide system information: |
| 55 | + - Ruby version |
| 56 | + - Capistrano version |
| 57 | + - Sidekiq version |
| 58 | + - Systemd version (if relevant) |
| 59 | + |
| 60 | +## Development Setup |
| 61 | + |
| 62 | +```bash |
| 63 | +# Clone the repo |
| 64 | +git clone https://github.com/seuros/capistrano-sidekiq.git |
| 65 | +cd capistrano-sidekiq |
| 66 | + |
| 67 | +# Install dependencies |
| 68 | +bundle install |
| 69 | + |
| 70 | +# Run tests |
| 71 | +bundle exec rake test |
| 72 | + |
| 73 | +# Run tests in Docker |
| 74 | +docker build -t capistrano-sidekiq-test test/ |
| 75 | +docker run capistrano-sidekiq-test |
| 76 | +``` |
| 77 | + |
| 78 | +## Release Process |
| 79 | + |
| 80 | +Releases are managed by maintainers. The process is: |
| 81 | + |
| 82 | +1. Update version in `lib/capistrano/sidekiq/version.rb` |
| 83 | +2. Update CHANGELOG.md |
| 84 | +3. Run tests |
| 85 | +4. Build gem: `bundle exec rake build` |
| 86 | +5. Release: `bundle exec rake release` |
| 87 | + |
| 88 | +## Questions? |
| 89 | + |
| 90 | +Feel free to open an issue for any questions about contributing. |
0 commit comments