Implement CodeClimate (self-hosted) #2489

New Issue

GiteaMirror · 2025-11-02T04:38:16-06:00

GiteaMirror commented

2025-11-02 04:38:16 -06:00

Originally created by @Extarys on GitHub (Nov 4, 2018).

Description

Since CodeCLimate integration is a paid feature of GitLab, it would be great if Gitea would find a way to implement CodeClimate code quality check on merging and maybe add a Stats tab to the repo to see the code coverage (and in the future maybe vulnerability scan, etc)

It would be a great addition since there is currently no self hosted software that do it for free (GitLab, I'm looking at you!)

I hope this is a good place to make such suggestion.

Originally created by @Extarys on GitHub (Nov 4, 2018). ## Description Since CodeCLimate integration is a paid feature of GitLab, it would be great if Gitea would find a way to implement CodeClimate code quality check on merging and maybe add a Stats tab to the repo to see the code coverage (and in the future maybe vulnerability scan, etc) It would be a great addition since there is currently no self hosted software that do it for free (GitLab, I'm looking at you!) I hope this is a good place to make such suggestion.

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:38:16 -06:00

GiteaMirror closed this issue

2025-11-02 04:38:17 -06:00

GiteaMirror commented

2025-11-02 04:38:17 -06:00

@lunny commented on GitHub (Nov 4, 2018):

Is the API and webhooks enough to integrate with CodeCLimate?

@lunny commented on GitHub (Nov 4, 2018): Is the API and webhooks enough to integrate with CodeCLimate?

GiteaMirror commented

2025-11-02 04:38:18 -06:00

@Extarys commented on GitHub (Nov 4, 2018):

Does gitea feature Code Quality feedback on merge request? I haven't started testing anything yet but couldn't find anyone on the web talking about gitea and CodeClimate and I'm new to CI/CD. I was looking for a GitLab equivalent that would gives me a lot of feedback on my repo's status.

@Extarys commented on GitHub (Nov 4, 2018): Does gitea feature Code Quality feedback on merge request? I haven't started testing anything yet but couldn't find anyone on the web talking about gitea and CodeClimate and I'm new to CI/CD. I was looking for a GitLab equivalent that would gives me a lot of feedback on my repo's status.

GiteaMirror commented

2025-11-02 04:38:18 -06:00

@davidak commented on GitHub (Nov 6, 2018):

That would be indeed nice to have, but maybe better as stand-alone project, so it can also support other code hosting plattforms.

There are other sites like CodeClimate, some even open source:

https://codacy.com/ (works great for python)
https://scrutinizer-ci.com/ (works great for python)
https://www.sonarqube.org/ (horrible Java application, parts open source)
https://www.feram.io/ (finds problems in code and suggest fix. they want to open source it later https://github.com/feramhq/feram/issues/18)
https://landscape.io/ (broken)

For code quality check AFTER each commit, you can use a CI like drone, but a service like CodeClimate can even check a PR BEFORE it is merged and even prevent merging of broken code. It can also provide nice statistics about the code quality over time!

@davidak commented on GitHub (Nov 6, 2018): That would be indeed nice to have, but maybe better as stand-alone project, so it can also support other code hosting plattforms. There are other sites like CodeClimate, some even open source: - https://codacy.com/ (works great for python) - https://scrutinizer-ci.com/ (works great for python) - https://www.sonarqube.org/ (horrible Java application, parts open source) - https://www.feram.io/ (finds problems in code and suggest fix. they want to open source it later https://github.com/feramhq/feram/issues/18) - https://landscape.io/ (broken) For code quality check AFTER each commit, you can use a CI like drone, but a service like CodeClimate can even check a PR BEFORE it is merged and even prevent merging of broken code. It can also provide nice statistics about the code quality over time!

GiteaMirror commented

2025-11-02 04:38:18 -06:00

@lunny commented on GitHub (Nov 7, 2018):

I think status API could be used by this service to do that like Drone or jenkins to do. Gitea has implemented status API but need more work on pull request UI.

@lunny commented on GitHub (Nov 7, 2018): I think status API could be used by this service to do that like Drone or jenkins to do. Gitea has implemented status API but need more work on pull request UI.

GiteaMirror commented

2025-11-02 04:38:19 -06:00

@Extarys commented on GitHub (Nov 10, 2018):

It would be awesome to be able to have something that can have an all-in-one free open source alternative. Right now most services can be linked to GitHub but it is not self-hosted. Some features of GitLab is paid and quite heavy.

@Extarys commented on GitHub (Nov 10, 2018): It would be awesome to be able to have something that can have an all-in-one free open source alternative. Right now most services can be linked to GitHub but it is not self-hosted. Some features of GitLab is paid and quite heavy.

GiteaMirror commented

2025-11-02 04:38:19 -06:00

@davidak commented on GitHub (Nov 10, 2018):

I just found a CI for Go that is open source (but only seem to work with GitHub). It might can get extended to work with other languages and code hosting plattforms. https://golangci.com/

But maybe to have a sane solution we should focus on integrating ANY CI with ANY code analysis tool for ANY language and just search for or build a plattform to collect and display results, like https://codecov.io/ and https://coveralls.io/ for code coverage. It shouldn't be too complex to replicate the statistic features of CodeClimate and others.

@davidak commented on GitHub (Nov 10, 2018): I just found a CI for Go that is open source (but only seem to work with GitHub). It might can get extended to work with other languages and code hosting plattforms. https://golangci.com/ But maybe to have a sane solution we should focus on integrating ANY CI with ANY code analysis tool for ANY language and just search for or build a plattform to collect and display results, like https://codecov.io/ and https://coveralls.io/ for code coverage. It shouldn't be too complex to replicate the statistic features of CodeClimate and others.

GiteaMirror commented

2025-11-02 04:38:19 -06:00

@stale[bot] commented on GitHub (Jan 9, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 9, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:38:19 -06:00

@Extarys commented on GitHub (Jan 10, 2019):

@davidak We could take the golangci open source version and include it in Gitea 🗡️ Nice research!

@Extarys commented on GitHub (Jan 10, 2019): @davidak We could take the golangci open source version and include it in Gitea :dagger: Nice research!

GiteaMirror commented

2025-11-02 04:38:20 -06:00

@stale[bot] commented on GitHub (Mar 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:38:20 -06:00

@alexanderadam commented on GitHub (Oct 23, 2019):

There's also Pronto, a self hosted tool for a variety of languages, frameworks and checks that might be relevant in this list.

For a proper support (like the experience users have on other services) there should be PR support through the API (like approvals and rejects — maybe even per line)). Otherwise we can "only" write comments to PRs.
And it obviously also need some integration from pronto itself but I guess wouldn't be too difficult because there are various possibilities for integrating Swagger with Ruby and there's also an old Ruby gem that could help as well.

So I would say that #5267 (this issue here) and #5733 (which adds the PR functionality via API) are at least a bit related (if done properly). 😉

@alexanderadam commented on GitHub (Oct 23, 2019): There's also [Pronto](https://github.com/prontolabs/pronto#pronto), a self hosted tool [for a variety of languages, frameworks and checks](https://github.com/prontolabs/pronto#runners) that might be relevant in [this list](https://github.com/go-gitea/gitea/issues/5267#issuecomment-436337190). For a proper support (like the experience users have on other services) there should be [PR support through the API](https://github.com/go-gitea/gitea/issues/5733) (like approvals and rejects — maybe even per line)). Otherwise we can "only" write comments to PRs. And it obviously also need [some integration from pronto itself](https://github.com/prontolabs/pronto/issues/275) but I guess wouldn't be too difficult because there are various possibilities for [integrating Swagger with Ruby](https://swagger.io/tools/open-source/open-source-integrations/#ruby) and [there's also an old Ruby gem that could help as well](https://github.com/megamsys/megam_gogs.rb). So I would say that #5267 (this issue here) and #5733 (which adds the PR functionality via API) are at least a bit related (if done properly). :wink:

GiteaMirror commented

2025-11-02 04:38:20 -06:00

@delvh commented on GitHub (Apr 29, 2023):

I don't see a reason why Gitea should get bloated like that.
As already mentioned, it's probably better to integrate it through a third-party service that fails your branch protection or something similar.

@delvh commented on GitHub (Apr 29, 2023): I don't see a reason why Gitea should get bloated like that. As already mentioned, it's probably better to integrate it through a third-party service that fails your branch protection or something similar.

GiteaMirror referenced this issue

2025-11-02 12:10:22 -06:00

[PR #2489] [MERGED] Open external wiki in new window #16426

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2489