Update usage for file name
What does this MR do?
Updates the usage of 'file name' (two words) to 'filename' one word, as per the word list.
Changes to usage in GraphQL docs will be in a separate MR.
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
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.
Merge request reports
Activity
assigned to @fneill
- A deleted user
added Architecture Evolution Blueprint development guidelines labels
2 Warnings 
31e8ab5d: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. be4fb59f: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 3 Messages 
This merge request might require a review from a Coach Engineer. This MR contains docs in the /development directory. Any Maintainer, other than the author, can merge. You do not need tech writer review. 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. Architecture Evolution Review
This merge request might require a review from a Coach Engineer.
Following files, that may require the additional review, have been changed:
doc/architecture/blueprints/ci_pipeline_components/index.md
Documentation review
The following files require a review from a technical writer:
-
doc/administration/audit_event_streaming/audit_event_types.md(Link to current live version) -
doc/administration/backup_restore/backup_gitlab.md(Link to current live version) -
doc/administration/backup_restore/backup_large_reference_architectures.md(Link to current live version) -
doc/administration/backup_restore/index.md(Link to current live version) -
doc/administration/backup_restore/troubleshooting_backup_gitlab.md(Link to current live version) -
doc/administration/gitaly/configure_gitaly.md(Link to current live version) -
doc/administration/logs/log_parsing.md(Link to current live version) -
doc/administration/operations/rails_console.md(Link to current live version) -
doc/administration/troubleshooting/linux_cheat_sheet.md(Link to current live version) -
doc/administration/instance_limits.md(Link to current live version) -
doc/administration/license_file.md(Link to current live version) -
doc/administration/repository_storage_paths.md(Link to current live version) -
doc/administration/server_hooks.md(Link to current live version) -
doc/api/packages/debian.md(Link to current live version) -
doc/api/packages/helm.md(Link to current live version) -
doc/api/packages/pypi.md(Link to current live version) -
doc/api/discussions.md(Link to current live version) -
doc/api/integrations.md(Link to current live version) -
doc/api/projects.md(Link to current live version) -
doc/api/search.md(Link to current live version) -
doc/api/secure_files.md(Link to current live version) -
doc/architecture/blueprints/ci_pipeline_components/index.md(Link to current live version) -
doc/ci/cloud_deployment/index.md(Link to current live version) -
doc/ci/jobs/job_artifacts_troubleshooting.md(Link to current live version) -
doc/ci/pipelines/settings.md(Link to current live version) -
doc/ci/runners/configure_runners.md(Link to current live version) -
doc/ci/testing/code_quality.md(Link to current live version) -
doc/development/documentation/testing.md(Link to current live version) -
doc/integration/advanced_search/elasticsearch_troubleshooting.md(Link to current live version) -
doc/update/package/package_troubleshooting.md(Link to current live version) -
doc/update/deprecations.md(Link to current live version) -
doc/user/application_security/api_fuzzing/index.md(Link to current live version) -
doc/user/application_security/dast/checks/78.1.md(Link to current live version) -
doc/user/application_security/dast_api/index.md(Link to current live version) -
doc/user/application_security/policies/scan-execution-policies.md(Link to current live version) -
doc/user/application_security/vulnerabilities/index.md(Link to current live version) -
doc/user/group/import/index.md(Link to current live version) -
doc/user/project/merge_requests/ai_in_merge_requests.md(Link to current live version) -
doc/user/project/merge_requests/creating_merge_requests.md(Link to current live version) -
doc/user/project/repository/code_suggestions/index.md(Link to current live version) -
doc/user/project/repository/signed_commits/ssh.md(Link to current live version) -
doc/user/project/repository/index.md(Link to current live version) -
doc/user/project/repository/push_rules.md(Link to current live version) -
doc/user/project/repository/web_editor.md(Link to current live version) -
doc/user/project/web_ide/index.md(Link to current live version) -
doc/user/free_push_limit.md(Link to current live version) -
doc/user/ssh.md(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.mdfiles that you've changed. The first few lines of each*.mdfile 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.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend @wandering_person
(UTC+7, 7 hours ahead of author)
@mbobin (UTC+2, 2 hours ahead of author)
Please check reviewer's status!
-
Reviewer is available!
-
Reviewer is unavailable!
Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-reviewjob that generated this comment.Generated by
Edited by Ghost User
- A deleted user
added backend label
