### Overview Whenever possible, it’s recommended to work in a common Git repository and use branching strategies to manage your work. However, if you do not have write access for the repository you want to contribute to, you can create a fork. Forking enables important workflows which allow for seamless contribution to open source and open core projects. ### Problem While the basic forking workflows are well supported in GitLab today, there are a number of use cases that must be supported to delight our users, namely: 1. Easily create merge requests from confidential issues 1. Access all forks as "source" when creating a merge request 1. Compare views across forks 1. Cherry pick across forks The issues in this epic will give us parity with the competition. At that point we'll move to [🍴 ❤️ Make forking workflows loveable](https://gitlab.com/groups/gitlab-org/-/epics/264).