Move files into files/ directory
What does this MR do?
As part of the left nav work in https://gitlab.com/gitlab-org/gitlab/-/issues/457784, let's make the underlying file structure match what we say in the left nav. These pages were moved:
- Old:
doc/user/project/repository/csv.md
- New:
doc/user/project/repository/files/csv.md
- Old:
doc/user/project/git_attributes.md
- New:
doc/user/project/repository/files/git_attributes.md
- Old:
doc/user/project/repository/git_blame.md
- New:
doc/user/project/repository/files/git_blame.md
- Old:
doc/user/project/repository/git_history.md
- New:
doc/user/project/repository/files/git_history.md
If you check the left nav for https://docs.gitlab.com/ee/user/project/repository/files/index.html you'll see these pages are already listed as child pages of "File management." This MR moves the files, and updates links to / from these files.
gitlab-docs
MR to update the left nav: Updates items under repository/files in nav (gitlab-docs!4874 - merged)
Related issues
- Related to https://gitlab.com/gitlab-org/gitlab/-/issues/457784+
- Related to Updates items under repository/files in nav (gitlab-docs!4874 - merged)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product availability details under the H1 topic title. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.