The previous URL had two drawbacks:

1. It didn't match what the title was about (`Assignments to DevOps
   Stages and Groups`, and the anchor was `#designated-technical-writers`).
2. It didn't account for the other sections, like development and API
   guidelines.

This comes after a recent issue was diagnosed for one of our customers
where the plugin was causing the integration not to work. Hopefully
calling out plugins in our docs may save some time as customers may be
able to spot early on that the plugin is the thing causing issues before
asking us to diagnose the problem. Since there are many plugins that are
3rd party to Elasticsearch and they can significantly change the
behaviour of Elasticsearch it's impossible for us to test against all
plugins and be sure what does and does not work.

Related to: gitlab-org/gitlab#284446

This extract the Experiment struct and creates a separate class. We also
removed the `environment` since we never used it and can implement again
if needed. For now we only run experiments on Gitlab.com and on dev
environment.

Lucas Charles authored 4 years ago and Nick Gaskill committed 4 years ago

Update requirements with link to supported distributions

This MR enables Group SAML Group Sync by default, as well
as addressing a minor policy issue and moving the feature
from Ultimate/Gold to Premium/Bronze.

Dan Jensen authored 4 years ago and Phil Hughes committed 4 years ago

Previously the admin interface for "User and IP Rate Limits" had inputs
with duplicate labels. These inputs were only differentiated by their
groupings on the page, which themselves were not clear. This improves
the input labels, makes the checkbox labels bold (as they are the most
important inputs in this section), and adds some horizontal rules to
visually distinguish the groupings. These changes are intended to make
this UI easier to understand, and match up better with the docs.

`Use Docker socket binding` is an alternative to [TLS
enabled](https://gitlab.com/gitlab-org/gitlab/-/blob/05ce22b8869cd308bcd259537eefd03ecf5f8f0e/doc/ci/docker/using_docker_build.md#L147)
and [TLS
disabled](https://gitlab.com/gitlab-org/gitlab/-/blob/05ce22b8869cd308bcd259537eefd03ecf5f8f0e/doc/ci/docker/using_docker_build.md#L244).
There is `Enable registry mirror for docker:dind service` in between
them which is unrelated.

Emily Ring authored 4 years ago and Bob Van Landuyt committed 4 years ago

Updated api to include project_approval_rules show
Updated associated tests

Sean Arnold authored 4 years ago and Alessio Caiazza committed 4 years ago

Workhorse version bump to v8.55.0 to support direct_upload on the new API endpoint

Marcel Amirault authored 4 years ago and Suzanne Selhorn committed 4 years ago

Make sure to use this -> noun, or rephrase. Cleans
up other minor issues surrouding the fixed language
as well

Cleaning up yet more future tense goodness.

Dan Jensen authored 4 years ago and Ezekiel Kigbo committed 4 years ago

This re-names the Instance Statistics feature as Usage Trends in the
UI (not in the code itself).

Simon Knox authored 4 years ago and Ash McKenzie committed 4 years ago

Also accept a global id when querying the `iterations`
field

But maintain backward compatibility by accpeting
a raw model id

More files in the development directory that used future tense
instead of present tense.

These pages used future tense, instead of the present tense, which
is GitLab tone and style. No substantive changes to content were made.

Project-level Issue Analytics was introduced after group-level Issue
Analytics, with documentation that simply pointed to the original
group-level documentation. That caused the documentation to be more
complex than it needed to be, and also caused the documentation left-
nav to behave incorrectly. This introduces a separate page for the
project-level feature to fix these problems.

Amy Qualls authored 4 years ago and Craig Norris committed 4 years ago

These unowned docs need future tense scrubbed out of them too!

Amy Qualls authored 4 years ago and Craig Norris committed 4 years ago

Shift from future tense to present tense.

These pages don't have owners, but still need instances of future
tense scrubbed out.

Dallas Reedy authored 4 years ago and Mike Jang committed 4 years ago

Shift 'we' to 'you' language, clean up line endings, update word
choice to be closer to GitLab tone and style.

The group formerly known as Manage:Analytics was briefly re-named
Manage:Value Stream Management before being ultimately re-named
Manage:Optimize. This updates the deprecated references to
Value Stream Management in the documentation to be Optimize.