feature_flags docs: fix link anchor to Unleash SDKs

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

What does this MR do?

It updates the anchor in the link to the list of Unleash SDKs because the existing link was broken.

Related issues

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details 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 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.

Thanks for your contribution to GitLab @tanyabouman!

• If you need help, page a coach by clicking here or come say hi on Discord.
• When you're ready, request a review by clicking here.
• We welcome AI-generated contributions and offer complimentary access to GitLab Duo!

This message was generated automatically. Improve it or delete it.

added 1st contribution Community contribution workflowin dev labels

assigned to @tanyabouman

changed the description

added docs-only label

	2 Warnings
	This merge request does not refer to an existing milestone.
	Labels missing: please ask a reviewer or maintainer to add documentation to this merge request.

	1 Message
	This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive.

Documentation review

The following files require a review from a technical writer:

• doc/operations/feature_flags.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

@gitlab-bot help

Posted via contributors.gitlab.com.

requested review from @kushalpandya

added 1 commit

• faab17e7 - Feature_flags: fix link anchor to Unleash SDKs

Compare with previous version

mentioned in issue gitlab-org/quality/triage-reports#22490 (closed)

requested review from @marcel.amirault and removed review request for @kushalpandya

added devopsdeploy documentation groupenvironments maintenancerefactor typemaintenance labels

added sectioncd label

changed milestone to %17.10

resolved all threads

added 363 commits

• faab17e7...a5d076c0 - 362 commits from branch gitlab-org:master
• 7dc2422d - Feature_flags: fix link anchor to Unleash SDKs

Compare with previous version

	1 Message
	This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive.

Documentation review

The following files require a review from a technical writer:

• doc/operations/feature_flags.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

started a merge train

merged

mentioned in commit b92d561b

Hi @tanyabouman

See where you rank! Check your spot on the contributor leaderboard and unlock rewards.

---

How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

Thanks for your help!

This message was generated automatically. Improve it or delete it.

Hi @marcel.amirault ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. Improve it or delete it.

added Technical Writing label

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#10822 (closed)

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#10823 (closed)

added workflowstaging-canary label and removed workflowin dev label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label