Pull updates from upstream repository into fork
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=21302) </details> <!--IssueSummary end--> When I fork a project, I want to be able to keep it up to date with the upstream project easily if not automatically. Original request: > I have forked project A in GitLab and create B and made some modification. After a month now i would like to update B project by pulling changes done in A. > > How can i do this? I have option to create Merge request but i could't able pull from A. > > I know this could be very simple because if anyone like to contribute has eventually take pull before submitting merge request. ### Further details From [Twitter](https://twitter.com/nathankpeck/status/1085291025143382017): > My biggest @github feature wish is that there was a button to easily catch my fork up to whatever point the remote is at now. It's still super weird to me that I have to go into the command line and do all these manual steps to do this: https://help.github.com/articles/syncing-a-fork/ Interestingly Github previously had this feature in the form of a [fast forward](https://github.blog/2008-12-12-fast-forward-your-fork/) button. It is unclear when this feature was removed. This is a common workflow that has been documented by: - GitLab with a blog post: https://about.gitlab.com/2016/12/01/how-to-keep-your-fork-up-to-date-with-its-origin/ - Github with documentation: https://help.github.com/articles/syncing-a-fork/ ### Proposal Add a **Pull new updates from upstream repository into my fork** button ### Links / references - https://about.gitlab.com/2016/12/01/how-to-keep-your-fork-up-to-date-with-its-origin/ - https://github.blog/2008-12-12-fast-forward-your-fork/
issue