Gitlab repos listed under "Other"

[Kupofty]

The problem

If the repo is hosted on gitlab.com (not self-hosted), the owner should be populated automatically.
You should do the following:
From the GitHub Desktop window, open the developer tools by pressing Ctrl+Shift+I
Go to the "Network" tab
Refresh the window by pressing Ctrl+Alt+R
See if any API request in the Network tab returned an error code

I created this issue to continue the discussion and to avoid polluting #48

Here's the result of the API requests, I don't see any errors :

Release version

3.5.5-beta1 (x64)

Operating system

Ubuntu 24.04

Steps to reproduce the behavior

• Download a respository from my private Gitlab group (hosted on gitlab.com)
• Open the repo tree
• Repo listed under "Other"

I tried with multiple repos from this group (adding local repo and cloning directly from the Gitlab repo list (my gitlab account is connected in Github desktop plus).

it works fine with public repo I found and cloned.

Screenshots

The "Installation_Kit" is a repository from gitlab (hosted on gitlab.com) but still showed as "Other"

[pol-rivero]

I haven't been able to reproduce the error. This is what I did:

1. Create a private group on gitlab.com, and create a private project/repo inside the group.

2. Clone the repo and add it to GitHub Desktop Plus.

3. The repo is listed under the correct name.

---

Please let me know if I'm missing something.

Also, could you check if the branches list in the "Installation_Kit" repo has a "Pull Requests" tab?

[Kupofty]

I created a new personal private group and repository on GitLab.com, and everything worked as expected — the "Pull Requests" tab is visible.

However, when I select a repository from my dev team, the "Pull Requests" tab does not appear.
I guess the issue must be related to how the group was set up...

[pol-rivero]

Hi, I wanted to let you know that I'll be very busy for a few months and won't have much time to dedicate to this project.
I'll probably prioritize keeping up with the upstream and getting the multiple accounts feature to the finish line in the limited time that I'll have.
Therefore, I won't be working on this issue for now.

@Kupofty since you can now set the repository group manually (#48), the only thing you are missing is the pull requests integration.

If anyone wants to contribute a fix and can reproduce the error, a good place to start looking would be RepositoriesStore.setGitHubRepository. Put a breakpoint there and add a repository that does work, look at the stack trace in the debugger to see the code path that was followed. Then add the repository that doesn't work and manually follow the same code path in the debugger to see where they differ.