FEATURE REQ - GitLab integration

[AetherYT]

The feature request

Anyway GitLab integration can be added? It's really messy with personal access tokens right now..

Proposed solution

Add sign-in or PAT support for GitLab (like Bitbucket has been added)

Additional context

No response

[pol-rivero]

Do you want this integration to be able to clone / commit to repositories? Or to show rich information in-app (such as PRs)?

If it's to clone / commit, the integration will not help you. You will need to set up SSH keys anyway (it's actually really easy, just run ssh-keygen -t ed25519, copy the contents of ~/.ssh/id_ed25519.pub and paste them in your GitLab profile > SSH Keys > Add new key). After doing that, you should be able to clone your repos (use SSH instead of HTTPS for cloning!) and commit to them indefinitely, without having to worry about personal access tokens.

If it's to show PRs, etc., I agree that a GitLab integration would be a nice addition, but it will take some time as I'm very busy at the moment. If you want to give it a try, you can search for all occurrences of bitbucket in the source code.

[pol-rivero]

Labeling this issue as help wanted, since I don't currently use GitLab and don't have the bandwidth to implement this.

I'm open to a PR if anyone is interested in implementing this. If you want to give it a shot, search for the string "bitbucket" in the source code, and make the required extensions in each result. This includes:

• In github-repository.ts, add a new gitlab value to the RepoType union type.
• Implement OAuth login for GitLab. I believe their "Authorization code with Proof Key for Code Exchange (PKCE)" method is what you are looking for.
  • This is by far the hardest part. If you manage to get it working, the rest of the implementation will be long but very easy.
  • See the current GitHub and Bitbucket implementations for inspiration. If you need to handle a refresh token, see how it is done in the Bitbucket implementation.
• In api.ts:
  • Create a class GitLabAPI that extends API and overrides the appropriate methods to call the correct GitLab API endpoints.
  • Implement the GitLab API output schema as interfaces and implement methods to convert them to GitHub's interfaces. For example, see IBitbucketAPIPullRequest and toIAPIPullRequest.
  • In fetchUser and fromAccount, instantiate GitLabAPI if the endpoint is GitLab's API.
• Keep searching for "bitbucket" occurrences to implement the missing GitLab UI or menu texts.
• Keep using the UI and looking for API errors in the console, and keep overriding methods in GitLabAPI as required.

[thangckt]

hi @pol-rivero,

Any progress? did you refer to GitKraken's approach?

[pol-rivero]

@thangckt I actually hadn't started yet, but I might have time to implement this soon. I'll probably generate a starting point with the new copilot feature in GitHub, it has given me good results before so that might speed up the process.

Keep in mind that this integration is mainly for viewing and creating pull requests. For cloning, pulling and pushing repos you will need to set up SSH keys as explained here.

[jskye]

would be cool to have same integration for gitea/forgejo too

[pol-rivero]

@jskye I don't think either of those could be supported at the moment, because both of them are self-hosted, and the current system doesn't really account for that.

However, I'm always open to PRs, so feel free to contribute if you need support for those.

[pol-rivero]

This is now shipped in the latest alpha build. Feel free to check it out and tell me if you find any errors.