Skip to content

Redact outdated GitLab Flow video from MR page

Amy Qualls requested to merge 392859-aqualls-redact-video into master

What does this MR do?

As described in Docs feedback: GitLab Flow video still uses "Ma... (#392859 - closed), the GitLab Flow video at https://www.youtube.com/watch?v=InKNIvky2KE has multiple problems. As part of the work in Gitlab Flow Docs - Adding Enablement Content fo... (#378297 - closed) to remove the related (and similarly outdated) GitLab Flow page from the documentation, it made sense to also take down the link to this video.

@csaavedra1, there's previous discussion (#392859 (comment 1288642782)) between @phikai and @heather about what to do with this video. I don't know if you intend to create an updated version of the video. If you think it's worthwhile, please create an issue in the appropriate project. My goal here is to finish my involvement in the project of cleaning out this outdated info from the GitLab docs. If a new version gets created, make a merge request to propose adding links to it in the docs.

For now, let's get this line taken out of the merge requests page.

Related issues

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.
Edited by Amy Qualls

Merge request reports