Gitea support #80

Open thugcee opened 5 years ago

Gitea is a community managed fork of Gogs, lightweight code hosting solution written in Go and published under the MIT license.

More info at https://gitea.io

Gitea frequently pulls features from Gogs, so supporting Gitea will probably work for Gogs too.

How could something like this get implemented? Which steps in general and how can the Gitea community help?

How far is this support right now?

Any plans at all?

It is not directly on the roadmap but wouldn't be too hard to add. We are prioritising such integrations based on demand.

Since the Gitea's API v1 is simliar as Github API v3, I think it will not be too hard.

Would this be possible with self-hosted gitpod at the moment?

It is either supported for both hosted and self-hosted, or not at all.

The support has simply not been integrated yet.

It is either supported for both hosted and self-hosted, or not at all.

Correct!

The support has simply not been integrated yet.

Support for raw git URLs (https://github.com/gitpod-io/gitpod/issues/167) has been scheduled for the April 2021 milestone which would enable scenarios such as https://gitpod.io#https://try.gitea.io/cezar97/Gitea_Issue_Logout.git

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

Bump

On Mon, 14 Jun 2021, 12:30 pm stale[bot], @.***> wrote:

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

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gitpod-io/gitpod/issues/80#issuecomment-860325689, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA7C6P2BOSNHRDAV6CHS3LTSVSTRANCNFSM4FXJE3NQ .

So is this anywhere on the roadmap by now? This would be great to have...

Integrating with OAuth2 provider mode (https://docs.gitea.io/en-us/oauth2-provider/) it looks like this would be relatively low hanging. @AlexTugarev WDYT? can you provide a rough estimation?

The overview looks good, but it the lack of scopes let me wonder how to integrate it nicely. The authorize URL from the example lacks the scope parameter, and I'm not sure if this is mandatory in the passportjs libs. The Git Integrations page (and the backend) does not support the "empty scopes" case.

That said, though it looks fairly easy to integrate on the protocol level (< 1d), I see some risk in getting it to a useable state – at least it could require adding special handling.

Any update for this? I can't use gitpod with gitea private repos.

We are tracking requests for additional git providers. No updates a.t.m.

We are prioritising such integrations based on demand.

I really need this :). Would be nice if Gitea could be integrated soon.

I really need this :). Would be nice if Gitea could be integrated soon.

Wanna send in a pull-request that adds support? We would accept it.

Come join https://www.gitpod.io/chat in the contributing channel.

The approach would be to add a new context parser (see https://github.com/gitpod-io/gitpod/pull/5367) and integrate it with https://docs.gitea.io/en-us/oauth2-provider/

Would Gitpod be amenable to sponsoring a Gitea maintainer to submit a PR to Gitpod to support Gitea integration?

(I am one of the project leads of Gitea and am able to facilitate coordination with Gitea maintainers if the answer to above is yes)

This would be awesome...

Would love to see it too !

Would be nice if Gitea could be integrated soon...

I'd love to be able see this happen

is there a update? @svenefftinge @jldec

it would be a great improvement !

Looking at the code and places the integration of Bitbucket (probably a rather limited support compared to Github) was done with, it shouldn't be to hard to open a PR with basic Gitea support 😉

Looking at the code and places the integration of Bitbucket (probably a rather limited support compared to Github) was done with, it shouldn't be to hard to open a PR with basic Gitea support 😉

Gitpod would accept a pull request that adds support. :)

Would Gitpod be amenable to sponsoring a Gitea maintainer to submit a PR to Gitpod to support Gitea integration? (I am one of the project leads of Gitea and am able to facilitate coordination with Gitea maintainers if the answer to above is yes)

Happy to raise the amount of ongoing sponsorship to Gitea from Gitpod @techknowlogick once the integration is in place as part of our open-source sustainability fund as Gitea once integrated would officially be in Gitpod's bill of materials.

Here's how Gitpod approaches supporting software that makes Gitpod possible...

https://www.gitpod.io/blog/gitpod-open-source-sustainability-fund

In addition to this can upgrade the accounts of Gitea maintainers to complementary accounts 🚀

any update?

I did most of the unit test cases for the context. But thats a quite time consuming task to support all of those different kinds especially the edge cases. For example opening an PR by using the issue url with a PR id to open a PR with Gitpod. Testing the result is also pretty difficult as I need to spint up my own Gitpod cluster each time to test my changes with all other components, but the Gitpod team did an awesome job and recently released a single node version #9075 which is pretty fast in starting and may help me with developing the Gitea integration. I only need to find out how I can properly use it with a custom image. 🙈

PS: Posting you interest in this feature is pretty important I guess as it will convince the Gitpod team to accept my PR once its done 😉

I think your chances to get it accepted are pretty high anyway 😊

Any update about the integration of Gitea servers ?

Curious as well!

I just wanted to register my interest in this integration as well

@anbraten Did you upload the code somewhere, or can you do that?

https://github.com/gitpod-io/gitpod/pull/8131

Its quite some time since I worked on it. Main issue I had the last time was the deployment / debugging it.

gitpod-io / gitpod

Gitea support #80