3 ms·

> There are countless SaaS applications asking for full-repo access to Github (all the source code, with write access). Sentry does not request write access to

> There are countless SaaS applications asking for full-repo access to Github (all the source code, with write access). Sentry does not request write access to source code. It requests read/write access to issues and read access to source code. You can also see this on the documentation for the GitHub enterprise integration which lists the exact permissions required: https://docs.sentry.io/product/integrations/source-code-mgmt/github/ https://docs.sentry.io/product/integrations/source-code-mgmt...

sandstrom 5y ago
Thanks for clarifying. It would still be better if I didn't have to give read access to source code, but could still use the issues integration. But I agree it's not as a bad as write access to source code.
- michaelbuckbee 5y ago
  Most error monitoring services want this as they map errors to commits.
  - dharmab 5y ago
    As a user it's nice to have the option of foregoing the feature.
    - orf 5y ago
      Then just don’t link it to GitHub if you don’t want your errors tracked back to specific commits?
      - dharmab 5y ago
        I might want it linked to my issues but not my source code.
  - sandstrom 5y ago
    I know it's more work, but they could also use Github Actions to push recent commits (past 90 days) to themselves, and use them. That way they wouldn't store or have access to all source code.