getsentry / getsentry/sentry

Configure Github source code repository mapping without giving source-code access

Open
#60,510 10 comments 7 reactions 0 assignees View on GitHub
Component: Integrations Feature Product Area: Issues Scope: Backend
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

## Problem

We cannot setup [Sentry stack-trace source-code linking](https://docs.sentry.io/product/integrations/source-code-mgmt/github/#stack-trace-linking) without giving full access to our source-code. But technically this shouldn't be required.

The reason for not giving you full source-code access, is that if you get hacked (like Solarwinds or Heroku), we don't want the hacker to extract our source-code.

This works great with the Sentry CLI, which we are using in Github actions. But for source-code mapping, your system won't allow me to only fill in base-url to the repo and branch name, it requires the app to have access (even though that's not strictly required).

## Bugsnag

Bugsnag offer this without giving them access to source code.

![CleanShot 2023-11-23 at 13 59 26](https://github.com/getsentry/sentry/assets/122287/f30383df-274d-4db5-a0bd-62a41c65df62)

With Bugsnag, we'd set this using their CLI tool, which is one option. Another one would be to set it in the Sentry web UI somewhere.

https://docs.bugsnag.com/build-integrations/bugsnag-cli/create-build/#repository-repository

## UI that I wish would change

![CleanShot 2023-11-23 at 13 51 42](https://github.com/getsentry/sentry/assets/122287/59137f74-58e5-4d4b-b65f-1656bd160b9f)

### Solution Brainstorm

_No response_

### Product Area

Settings - Repositories

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.