03 FAQ
Forking of Repositories Fails
This applies to self-hosted Gitlab servers
GitLab's “default projects limit” setting applies to all users, but it's separate from the limitations placed on external users. External users have specific restrictions by default, such as being unable to create projects, unless access is explicitly granted. This setting cannot be changed.
As a result, external users cannot fork existing repositories, as forking technically means creating a new project in their own namespace.
If you're trying to fork a repository on code.hampel-soft.com and receive an error message saying you cannot create projects in your own namespace, please reach out to us directly via Discord, share the email or username you used to sign up on our GitLab server, and we can manually enable that option for you.
Cloning of Git Submodules Fails (CI)
When working with personal access tokens or from within the gitlab-runner, you might run into Permission denied (publickey) errors. If you are using GitLab 8.12+ and your submodule is on the same GitLab server, you must update your .gitmodules file to use relative URLs.
From the relevant documentation:
If you are using GitLab 8.12+ and your submodule is on the same GitLab server, you must update your .gitmodules file to use relative URLs. Since Git allows the usage of relative URLs for your .gitmodules configuration, this easily allows you to use HTTP(S) for cloning all your CI jobs and SSH for all your local checkouts. The .gitmodules would look like:
path = project
url = ../../group/project.git