The source project of this merge request has been removed.
Fix incorrect URL in GitLab.com integration sample
What does this MR do?
Documentation for MR !78556 (merged) mistakenly copied the custom instance URL from the custom GitLab integration sample to the GitLab.com integration sample. This was really confusing, since there are two GitLab instances at play here, and samples for GitLab.com and a custom GitLab instance were now identical except for the display name. This MR removes the URL from the GitLab.com sample again.
Review 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 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. - 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. -
Ensure a release milestone is set.