diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-08-12 15:11:32 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-08-12 15:11:32 +0300 |
| commit | ee772e0c77e11099a9f077f780cd1a18de803222 (patch) | |
| tree | 1221267468f0f9e0d9390c82402b70789a6ef53b /doc/development/sidekiq/compatibility_across_updates.md | |
| parent | 94a5041917eb74f9636a4c2a73b055cf2928a585 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/sidekiq/compatibility_across_updates.md')
| -rw-r--r-- | doc/development/sidekiq/compatibility_across_updates.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/sidekiq/compatibility_across_updates.md b/doc/development/sidekiq/compatibility_across_updates.md index a9897929596..1d369b5a970 100644 --- a/doc/development/sidekiq/compatibility_across_updates.md +++ b/doc/development/sidekiq/compatibility_across_updates.md @@ -28,7 +28,7 @@ others - particularly [latency-sensitive jobs](worker_attributes.md#latency-sens this will result in a poor user experience. This only applies to new worker classes when they are first introduced. -As we recommend [using feature flags](../feature_flags/) as a general +As we recommend [using feature flags](../feature_flags/index.md) as a general development process, it's best to control the entire change (including scheduling of the new Sidekiq worker) with a feature flag. |