You can contribute to this project in the following ways:
- Try out the master branch and provide feedback
- File a bug report or propose a feature
- Open a PR for bug fixes or implement requested features
- Give feedback to opened issues/pull requests
- Contribute documentation in the sentry-doc repo
And if you have any questions, please feel free to reach out on Discord.
- Use
bundle exec rake
to run tests.- In
sentry-rails
, you can useRAILS_VERSION=version
to specify the Rails version to test against. Default is6.1
- In
- Use example apps under the
example
orexamples
folder to test the change. (Remember to change the DSN first) - To learn more about
sentry-ruby
's structure, you can read the Sentry SDK spec
Please read the extension guideline to learn more. Feel free to open an issue if you find anything missing.
- Run the example app(s) of the gem and make sure all the events are reported successfully.
- Update the changelog's latest
Unreleased
title with the target version.
- Make sure all the new features are documented properly in the changelog. This includes but not limited to:
- Explanation of the feature.
- Sample code for the feature.
- Expected changes on the SDK's behavior and/or on the reported events.
- Some related screenshots.
- Prepare a PR in the sentry-doc repo to update relevant content depending on the changes in the new release.
In addition to all the steps listed above, you also need to:
- Write a migration guide to
- Outline the major changes done in this release.
- Explain why upgrading is beneficial.
- List all the breaking changes and help users make related changes in their apps.
- Update gem READMEs.
- May need to check related wizard files in the sentry-doc repo.
- Visit the
Prepare Release
workflow. - Click
Run workflow
. - Fill in the required fields and run the workflow.
- Once
sentry-ruby
is released, you need to bump the required version ofsentry-ruby-core
in the integration gems before releasing them.