-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitea / Gogs plugin #15738
Comments
Hey @alexanderadam, unfortunately, we don't have the bandwidth to write and support this integration today, nor do we have this on our roadmap. You still have an option though. You could enable releases and suspect commits using this method. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
What a pity |
@manuzope is this backlog then? |
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️ |
Any update on this? |
No, this is still in the backlog and not planned right now. |
This is the sequel of the Sentry plugin issue 145
Summary
Add a plugin, that is similar to the GitLab/GitHub/BitBucket integration, for Gitea/Gogs.
Motivation
Gitea and Gogs are git services like GitLab or Bitbucket. They are popular self-hosted and resource friendly alternatives and you will find various instances in the web.
It is obviously useful to integrate Sentry with Gitea/Gogs for companies, universities and other organisations that are hosting their instances.
Until this is fixed, no Gitea/Gogs user can't fulfil what Sentry is suggesting: linking to a repo.
Additional Context
Gitea vs GoGS API
Gitea is a fork of GoGS and Gitea has nowadays about 3'000 patches on top of GoGS, more maintainers, more functionality and bugs fixed that are still present in GoGS (that's the reason why I switched once). So if you are running in some API bug, you should keep that in mind.
Testing & developing against an API
Also you can simply test the API integration on the official test instance at
https://try.gitea.io/
. There you can also find the Swagger API definition. As you can see, JSON and HTTP are protocol wise the only requirements but there are also various ready-to-use Swagger libraries for Python.If you rather want to use a local Gitea instance, you might want to use the official Docker image (there's also a
docker-compose.yml
provided that you can use).There's also more on API authorisation in the documentation.
PS: People reading this, might also be interested in this issue (a Sentry webhook for Gitea).
The text was updated successfully, but these errors were encountered: