I personally think it might be something related with the repo itself?
This is its package.json
{
"dependencies": {
"@strapi/strapi": "4.25.8",
"@strapi/plugin-users-permissions": "4.25.8",
"@strapi/plugin-i18n": "4.25.8",
"@strapi/plugin-seo": "^1.9.8",
"better-sqlite3": "8.6.0"
}
}
Maybe is missing some Strapi dependency?
That’s the whole package.json btw
hmm I am sorry about that, let me ask my colleagues
a potential lead could be the following:
the repository you are trying to use, in GitLab, are you the direct owner? or could it be a project shared and that belong to an Organization?
It belongs to an organization but I have read/write access
It’s basically a gitlab repo that I created under a private organization
It shows up in the dropdown when selecting repositories and selecting the specific project. Maybe it needs some more permissions from gitlab?
it makes sense, thank you for the details; accoriding to my teammates it might be the issue as we don’t support yet Organization level project (I am still trying to confirm this at the moment)
in the meantime, could you have a try by using a projet directly owned by you, and not under the name of your Organization? in that way we will be directly aware if this is the issue
I’ll create the same repository in my account to confirm this is the case
indeed, that was the issue
interesting! thank you very much for the test.
by curiosity, do you know what is the level/your Role in the Organization?
I will forward this to the engineers of the Cloud and they will take care of it;
I wish you a good weekend, I hope this solution can fit you in the meantime
I’m just a developer so I presume developer permissions
unfortunately I don’t have an exact deadline, I created a ticket and engineers will work on it depending of their roadmap;
I’ll let you know as soon as the status change, thank you for your patience, have a nice week
Hi <@186278349281165313>
I did some investigating and it looks like you have the maintainer role for some of the groups of your organization, but you have the developer role on the single repositories.
To fix the issue you have to ask for the maintainer role on the repository you intend to use on Strapi Cloud. On my side I will implement a fix that hides the repositories in which you don’t have have that role so they can’t be selected during the project setup.
Thanks and have a nice day. 
Hey <@579749086731829258> 
Is there any chance that instead of using user based SSO that we could use gitlab service accounts to get access instead?
No, I’m sorry, currently it is not possible.
Oh I see 
The problem with user based SSO is that, for organisations, it could give read-access to repositories which are internal.
I understand your concern. As a workaround you could potentially create a new Gitlab user that has maintainer access to only the repo that you want to use with the cloud, and no access to the other repositories. This however cannot be a service account because it need to be able to go through our signup process.