diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-06 21:10:31 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-06 21:10:31 +0300 |
commit | eec8ec6e4ed7aea652141681749f82ca63e9fbf8 (patch) | |
tree | b643c4fa7894834830f2bc52f0005f8b7789dd14 /doc/development/feature_flags | |
parent | 6d3676d61064af469f2fa1171bec4575235c6739 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/feature_flags')
-rw-r--r-- | doc/development/feature_flags/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/feature_flags/index.md b/doc/development/feature_flags/index.md index 5ab31b29704..d9eb29a7b7f 100644 --- a/doc/development/feature_flags/index.md +++ b/doc/development/feature_flags/index.md @@ -149,7 +149,7 @@ created using the [Experiment Tracking template](https://gitlab.com/gitlab-org/g `worker` feature flags are used for controlling Sidekiq workers behavior, such as deferring Sidekiq jobs. `worker` feature flags likely do not have any YAML definition as the name could be dynamically generated using -the worker name itself, e.g. `run_sidekiq_jobs_AuthorizedProjectsWorker`. Some examples for using `worker` type feature +the worker name itself, for example, `run_sidekiq_jobs_AuthorizedProjectsWorker`. Some examples for using `worker` type feature flags can be found in [deferring Sidekiq jobs](#deferring-sidekiq-jobs). ## Feature flag definition and validation @@ -348,7 +348,7 @@ Use the `push_frontend_feature_flag` method which is available to all controller ```ruby before_action do - # Prefer to scope it per project or user e.g. + # Prefer to scope it per project or user, for example push_frontend_feature_flag(:vim_bindings, project) end |