mirror of
https://github.com/Unleash/unleash.git
synced 2024-10-18 20:09:08 +02:00
0060697c01
As discovered in the recent segments breakathon, the docs aren't very clear about how conflicts are handled. This PR better documents when they can't be deleted or moved. It also mentions the edge case where a segment is used in an archived flag (it still can't be deleted, so you must either delete the flag, or revive it and remove the segment) |
||
|---|---|---|
| .. | ||
| api/legacy/unleash | ||
| integrations | ||
| sdks | ||
| activation-strategies.md | ||
| api-tokens-and-client-keys.mdx | ||
| archived-toggles.md | ||
| banners.md | ||
| change-requests.md | ||
| custom-activation-strategies.md | ||
| dependent-features.md | ||
| environments.md | ||
| event-log.md | ||
| event-types.mdx | ||
| feature-flag-naming-patterns.mdx | ||
| feature-toggle-types.md | ||
| feature-toggle-variants.md | ||
| feature-toggles.mdx | ||
| front-end-api.md | ||
| impression-data.md | ||
| login-history.md | ||
| maintenance-mode.mdx | ||
| network-view.mdx | ||
| notifications.md | ||
| playground.mdx | ||
| project-collaboration-mode.md | ||
| projects.md | ||
| public-signup.mdx | ||
| rbac.md | ||
| segments.mdx | ||
| service-accounts.md | ||
| sso.md | ||
| stickiness.md | ||
| strategy-constraints.md | ||
| strategy-variants.md | ||
| tags.md | ||
| technical-debt.md | ||
| unleash-context.md | ||
| whats-new-v4.md | ||