### Problem to solve Given you work on a company with the rule, that all code is saved on internal servers. 1. The company decides to publish some code as open source. 1. Then you need to setup an repo on gitlab.com 1. create an ci job for syncing etc. You still have the problem of MRs and Issues, which are out of sync. ### Intended users * Single Users with own instance * Companies who publish OS components ### Further details ### Proposal * Add option to sync a repository content with gitlab.com In the longterm you could also add an option to connect issues / MRs of the two instances or a full sync. This would add a huge benefit compared to gitlab.com, remeber the near east users, who just got cut of their repositories due to strange foreign affairs politics. ### Permissions and Security * local r/w repository * gitlab.com w to repository ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? * [ ] Single or triple click solution to publish and sync a repository with gitlab.com * [ ] Links from both instances to each other ### Links / references