Support creating Gitlab fork setup appropriately for a new feature
Similar to #4, but for Gitlab instead of Phabricator.
Would need to use the GitLab Projects API for this, most likely, requiring users to setup a personal API token.
More discussion was provided on the kde-devel mailing list in the Gitlab Evaluation & Migration thread. In particular we'd want this to not just pre-emptively create a new fork every time a repo is cloned but would need to be manually requested.
This would permit users to work on a long-running feature branch and be able to push it back to our Gitlab infra even without being able to immediately push to the authoritative repository itself.