The community member has a private GitLab repo link that is not being accepted by the Apify platform, showing the error "Git URL is not valid". The community members discuss potential solutions, such as adding a "deploy key" to the repo and checking the format of the URL. One community member suggests that the issue may be due to the nested folders in the repo URL, and provides an example of a different format that may work. The community members continue to troubleshoot the issue, with one member providing their exact GitLab URL and a link to their Apify actor, and another member eventually identifying the problem as the use of two slashes in the URL, which is no longer allowed. The solution provided is to use a different format for the URL, with the folder name coming after the colon.
I have a private GitLab repo link simillar to the following: git@gitlab.com:username/folder-1/folder-2/my-scraper.git The page showing that "Git URL is not valid". How can we solve that?
Hi, I added the deployment key. It's about the Git URL that is not valid by Apify Console. It was valid before. As you can see in the example, the repo my-scraper is nested into folders "folder-1" and "folder-2" (called groups and subgroups on GitLab). This link is supposed to work as it was before.
