Commit 5a59c6dc authored by Kati Paizee's avatar Kati Paizee Committed by Grzegorz Bizon

Fix kramdown issue in Verify docs

parent 539108d3
...@@ -189,8 +189,7 @@ Slack channel (GitLab team members only). ...@@ -189,8 +189,7 @@ Slack channel (GitLab team members only).
After your merge request is merged by a maintainer, it is time to release it to After your merge request is merged by a maintainer, it is time to release it to
users and the wider community. We usually do this with feature flags. users and the wider community. We usually do this with feature flags.
While not every merge request needs a feature flag, most merge While not every merge request needs a feature flag, most merge
requests in Verify should have feature flags. [**TODO** link to docs about what requests in Verify should have [feature flags](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#when-to-use-feature-flags).
needs a feature flag and what doesn’t].
If you already follow the advice on this page, you probably already have a If you already follow the advice on this page, you probably already have a
few metrics and perhaps a few loggers added that make your new code observable few metrics and perhaps a few loggers added that make your new code observable
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment