cannot fork: Gitlab repository does not exist
- Impacted Application: gitlab
- Affected application/URL: https://gitlab.e.foundation/e/os/android_vendor_eos/
The problem
I can't fork an older repo to make a merge request (will say "Gitlab repository does not exist"). I can fork other, esp. newly created repositories though.
Steps to reproduce
- use a regular new gitlab user and fork
android_vendor_eos - see
Gitlab repository does not exist
Technical details
This SO answer says it's about gitlabs internal cache or not-migrated-to-hashed-storage repositories and suggests a rake command.
Background
/e/OS team devs mostly do not need forks, they have branch creation permissions in the original repos and will not notice.
Gitlab can't do MRs from patches alone (gerrit style), so to create a MR I have to go through a fork sadly.
I do not know how helpful external code contributions are, they always need attention, but maybe a good idea anyway to look at the underlying issue.
Edited by tcecyk