Skip to content
This repository has been archived by the owner on Jun 12, 2023. It is now read-only.

Latest commit

 

History

History
83 lines (52 loc) · 2.81 KB

CONTRIBUTING.md

File metadata and controls

83 lines (52 loc) · 2.81 KB
Raw

Contributing

Requirements

You need:

  • nodejs 8 or higher
  • yarn 1 or higher
  • yalc (can be installed with yarn global add yalc)
  • http-server
  • ionic

Building

First install dependencies of the SDK (the root of the repository) This is only needed if dependencies are added/removed.

yarn

Once deps are installed, you can build the project:

yarn build

# Or in watch mode, for development

yarn watch

Updating Sentry Native packages

Android

  • Go to android/build.gradle and update the version of io.sentry:sentry-android.

iOS

  • Basically you'll need to edit SentryCapacitor.podspec and ios/Porfile updating the Sentry dependency and validate it on one of the examples apps on this project.
  • Run 'pod install --repo-update' on the ios folder and then 'yarn build' on the root folder.

Running the example apps

We use yalc to serve the local package builds to our example apps. You can run the bump scripts such as bump:v3 to package the SDK and sync the latest version to the example apps.

See the readmes in the specific example app folders for individual instructions:

Testing

yarn test

# Or the watcher when writing tests:
yarn test:watch

Changelog

We'd love for users to update the SDK everytime and as soon as we make a new release. But in reality most users rarely update the SDK. To help users see value in updating the SDK, we maintain a changelog file with entries split between two headings:

  1. ### Features
  2. ### Fixes

We add the heading in the first PR that's adding either a feature or fixes in the current release. After a release, the changelog file will contain only the last release entries.

When you open a PR in such case, you need to add a heading 2 named ## Unreleased, which is replaced during release with the version number chosen. Below that, you'll add the heading 3 mentioned above. For example, if you're adding a feature "Attach screenshots when capturing errors on iOS", right after a release, and the pull request number is 123, you'd add to the changelog:

## Unreleased

### Features

* Attach screenshots when capturing errors on iOS ([#123](https://github.com/getsentry/sentry-capacitor/pull/123))

There's a GitHub action check to verify if an entry was added. If the entry isn't a user-facing change, you can skip the verification with #skip-changelog written to the PR description. The bot writes a comment in the PR with a suggestion entry to the changelog based on the PR title.