Repository navigation
Rewrite feature flag docs for rules, phases, and triggers - #3557
Merged
Merged
Conversation
Add new feature flag pages for rule-based flags (overview, getting started, evaluation, rules and evaluation context, phased rollouts, rollout groups, previews, managing flags, providers, and upgrading to rules). Move the existing pages to feature-flags/legacy and redirect the old targeting URLs there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
|
Pull request environment is available at https://stoctodocspr3557.z22.web.core.windows.net/. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
dylanlerch
commented
Nov 10, 2026
dylanlerch
commented
Nov 10, 2026
dylanlerch
commented
Nov 10, 2026
dylanlerch
commented
Nov 10, 2026
dylanlerch
commented
Nov 10, 2026
dylanlerch
commented
Nov 10, 2026
- Replace the evaluation sequence with an environment configuration section - Confirm that raising a percentage keeps existing users, and drop the provider refresh marker - Warn that a due trigger turns a phase back on after it's turned off - Correct context attribute matching to case-insensitive, per the provider specification tests Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Remove stale client identifier rotation references - Drop the Private Preview hint from the legacy overview - Use the Minimum version condition name and Select wording - Remove an unsupported claim about default values Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|  | ||
|
|
||
| Below is an example of evaluating the flag with slug `dark-mode` in C#: | ||
| ## Feature flags |
There was a problem hiding this comment.
do we care about duplicate headings?
There was a problem hiding this comment.
no need to change... just something i picked up
|
|
||
| Phases let you plan a feature flag's whole rollout in an environment up front, from the first internal users to everyone, and move through it one stage at a time. This page covers adding phases, setting triggers so phases turn on by themselves, and turning phases on and off by hand to move a rollout forward or roll it back. | ||
|
|
||
| ## Phases and triggers |
There was a problem hiding this comment.
I found this section overloaded... the rest add a phase extra is fine - can iterate later
|
Good first strike. Big walls of text originally was overwhelming but when pairing with Claude actually worked out pretty well. Do we need a tag line for feature flags :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature flags now use rules, phases, and triggers in place of the per-environment targeting form. Projects with existing flags stay on the legacy model until they're upgraded, so the old docs need to stay available.
Changes
Adds new pages under
feature-flags/with the latest documentation for rules. Existing pages moved tofeature-flags/legacy/with a banner pointing to the new docs.Resolves BMBB-1256