Skip to content

Remove outdated "Temporary solutions" section

John Gaughan requested to merge jgaughan-master-patch-21432 into master

What does this MR do?

While exploring for solutions for a customer having project import issues, I came across the "Temporary solutions" section of the GitLab (file export) documentation. The linked issue is six years old, and describes Foreground as a workaround when large project imports are failing. This was well before Direct Transfer was released in 15.6.

This docs section refers to an "import template" owned by the Reliability team, and links to https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues. gl-infra/reliability was moved to gl-infra/production-engineering some time ago, and the "import" issue template no longer exists.

While I haven't tracked down the commit when this issue template was removed, it seems safe to assume that this process was discontinued at some point. Therefore, this corresponding documentation should be removed.

Related issues

This MR came out of this discussion: https://gitlab.com/gitlab-com/request-for-help/-/issues/2155#note_2281252158

Author's checklist

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 like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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