Updating flags to confirm Dedicated
What does this MR do?
After the bulk update, we took a closer look at these badges and removed Dedicated
from pages that required admin access, others that required server access, and those that dealt with authentication.
For transparency, we are not 100% sure that all of these updates are correct. However, we felt it was better to remove Dedicated, than to promise that a feature was supported for Dedicated when it might not be.
Thoughts captured in this spreadsheet: https://docs.google.com/spreadsheets/d/1qwfdtPCJWwBt8e0ZKLvCFubJ2jX8coGcqn5vacfdrnw/edit?usp=sharing
Related issues
Related to: #439130 (closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product tier badge 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.
Merge request reports
Activity
changed milestone to %16.10
added docsimprovement documentation maintenancerefactor typemaintenance labels
assigned to @sselhorn
added Technical Writing label
requested review from @phillipwells
- Resolved by Suzanne Selhorn
@phillipwells Next one for you. Details in the header.
- A deleted user
added Solutions development guidelines labels
3 Messages This MR contains docs in the /doc/development directory, but any Maintainer (other than the author) can merge. You do not need tech writer review. This MR contains docs in the /doc/solutions directory and should be reviewed by a Solutions Architect approver. 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. Documentation review
The following files require a review from a technical writer:
-
doc/api/database_migrations.md
(Link to current live version) -
doc/api/instance_clusters.md
(Link to current live version) -
doc/api/search_admin.md
(Link to current live version) -
doc/api/sidekiq_metrics.md
(Link to current live version) -
doc/integration/alicloud.md
(Link to current live version) -
doc/integration/auth0.md
(Link to current live version) -
doc/integration/azure.md
(Link to current live version) -
doc/integration/bitbucket.md
(Link to current live version) -
doc/integration/ding_talk.md
(Link to current live version) -
doc/integration/facebook.md
(Link to current live version) -
doc/integration/github.md
(Link to current live version) -
doc/integration/gitlab.md
(Link to current live version) -
doc/integration/gitpod.md
(Link to current live version) -
doc/integration/google.md
(Link to current live version) -
doc/integration/index.md
(Link to current live version) -
doc/integration/oauth2_generic.md
(Link to current live version) -
doc/integration/oauth_provider.md
(Link to current live version) -
doc/integration/omniauth.md
(Link to current live version) -
doc/integration/openid_connect_provider.md
(Link to current live version) -
doc/integration/salesforce.md
(Link to current live version) -
doc/integration/saml.md
(Link to current live version) -
doc/integration/twitter.md
(Link to current live version) -
doc/security/crime_vulnerability.md
(Link to current live version) -
doc/security/responding_to_security_incidents.md
(Link to current live version) -
doc/security/ssh_keys_restrictions.md
(Link to current live version) -
doc/security/two_factor_authentication.md
(Link to current live version) -
doc/user/application_security/offline_deployments/index.md
(Link to current live version) -
doc/user/instance/clusters/index.md
(Link to current live version) -
doc/user/packages/debian_repository/index.md
(Link to current live version) -
doc/user/search/index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file 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.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
removed review request for @phillipwells
requested review from @ahergenhan
added docs-only label
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn
- Resolved by Suzanne Selhorn