New life for custom SCM integration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Hello!
There are number of requests (like getsentry/sentry#15738, getsentry/sentry#68525, getsentry/sentry#55461, getsentry/sentry#86675) for integration with git repositories other then github, bitbucket, gitlab.
I guess most of us need it just for suspect commit and maybe source context.
Solution Brainstorm
Could you restore this incredible useful feature? https://github.com/getsentry/sentry/pull/53187
i believe it won't require much maintenance and could be useful before big integration like github's will be implemented.
Product Area
Releases
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed implementation in getsentry/sentry#53187 and the related requests linked in the issue. Determine how custom SCM support should cover suspect commits and source context, then verify that the restored integration works for repositories beyond GitHub, Bitbucket, and GitLab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100