Skip to content

SSO folder: rename images to include milestone info

Amy Qualls requested to merge aqualls-sso-image-names into master

What does this MR do?

Updates all the images in doc/user/group/saml_sso/img/ to add version numbers:

./user/group/saml_sso/img/AzureAD-scim_provisioning.png
./user/group/saml_sso/img/Azure-manage-group-claims.png
./user/group/saml_sso/img/OneLogin-app_details.png
./user/group/saml_sso/img/Okta-SM.png
./user/group/saml_sso/img/AzureAD-claims.png
./user/group/saml_sso/img/azure_configure_group_claim.png
./user/group/saml_sso/img/OneLogin-userAdd.png
./user/group/saml_sso/img/Okta-attributes.png
./user/group/saml_sso/img/OneLogin-parameters.png
./user/group/saml_sso/img/Okta-GroupSAML.png
./user/group/saml_sso/img/Okta-advancedsettings.png
./user/group/saml_sso/img/Okta-linkscert.png
./user/group/saml_sso/img/OneLogin-SSOsettings.png
./user/group/saml_sso/img/okta_saml_settings.png
./user/group/saml_sso/img/okta_setting_username.png
./user/group/saml_sso/img/AzureAD-scim_attribute_mapping.png
./user/group/saml_sso/img/AzureAD-basic_SAML.png
./user/group/saml_sso/img/Okta-GroupAttribute.png

Related issues

Related to Track adding in version numbers to all images (#493994)

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