docs: Expand fork relationship documentation
What does this MR do?
I recently looked for details on the effects of a fork relationship on various aspects of a project. The 1st commit here is a start. Might some be missing, see checklist below?
Related issues
Author's checklist
-
Document "Remove fork relationship" on https://docs.gitlab.com/ee/user/project/settings/#advanced-settings -
Link to relevant docu pages from https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork -
Follow the Documentation Guidelines and Style Guide. -
[-] If applicable, update the permissions table.
-
[-] Link docs to and from the higher-level index page, plus other related docs where helpful.
-
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.