Create update a fork page

What does this MR do and why?

In this MR, a new page for Update a fork is added to the Use Git --> Basic operations section.

The information on this page is Git-related info from Update a fork from the command line and Push to a fork as an upstream member.

It is part of a larger issue to reorganize Git documentation to improve the user experience by separating GitLab UI and Git CLI tasks.

Navigation

- Basic operations
  - Create a project
  - Clone a repository
  - Create a branch
  - Stage, commit, and push changes
  - Stash changes
  - Add files to your branch
  - Merge your branch
  - Update a fork

Review app

• NEW Update a fork

Related issues

• Issue: #499459 (closed)
• Child item: #499466 (closed)
• MR to update navigation: Add nav item for new Update a fork page (gitlab-docs!5162 - merged)

changed milestone to %17.6

added Category:Source Code Management Technical Writing devopscreate documentation groupsource code maintenancerefactor sectiondev typemaintenance labels

assigned to @brendan777

added 1 commit

• ed9bffdc - Add Git-related fork information to Use Git section

Compare with previous version

added docs-only label

mentioned in merge request gitlab-docs!5162 (merged)

resolved all threads

added 1 commit

• c55fc765 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/topics/git/forks.md (Link to current live version)
• doc/user/project/merge_requests/allow_collaboration.md (Link to current live version)
• doc/user/project/repository/forking_workflow.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 2 commits

• 5e695089 - Fix indentation of code snippet
• 9078d5a1 - Updated WARNING to NOTE

Compare with previous version

resolved all threads

added 1 commit

• 54a2e11e - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

marked this merge request as ready

requested review from @fneill

Hi @fneill Can you review this MR?

changed the description

changed the description