This page reuses the H1 title as an H2. It's an edge case that
Visual Studio Code doesn't catch, frustratingly enough. It causes
problems with duplicated linking to the two subheadings.

Small changes for active verbs in
agreement with their subjects.

Add more details about the file locations to clarify which file will be
used when multiple files are present in the repository

Closes: https://gitlab.com/gitlab-org/gitlab/-/issues/395131

Updating gems to support markdown for dbml and db2

Changelog: changed
EE: true

Alphabetize lines. Add back a missing
quotation mark.

With this change we are making policy changes for SAML group lock
which will prevent owners to add new members to the group in case SAML group lock is there

Changelog: added

Frontend suggestion applied

Text regenerate run

Structure.sql master

Structure sql fixed

Text change suggestion

Remove group method for lock_saml_membership

Structure.sql fixed

Added project policy check

Text internationalization changes

Context simplified

Changes for re-arranging specs

Feature issue: https://gitlab.com/gitlab-org/gitlab/-/issues/367547

Rename traits with _config postfixed
Fix job artifact public test
Update artifacts:public doc
Add tests when feature flag is disabled and refactor

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/109860

Sets the setting to 'soft' if :soft_email_confirmation
feature flag is on

Changelog: changed

Documentation changed for gem update guidelines now require builds on
all supported platforms instead of review by C language expert.

Removes note about making sure this migration runs. The reason is that
if we do todo sanitization, we should rather sanitize all existing
todos because there are probably some other edge cases when a todo is
not deleted. Or even better we might be able to avoid doing this todo
sanitization at all.

Either way, there is no reason to run this sanitization as it will be
superseded by different solution (or more general migration).

A custom lefthook target to run all the linters with with auto-fix
capabilities, but just on the files which changed in your branch.

```shell
# If installed globally
lefthook run auto-fix
# Or if installed via ruby gem
bundle exec lefthook run auto-fix
```

Fixed in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/102419

This page is being removed; take out the links to it.

The instance-level "Security dashboard", "Vulnerability report" and
their settings have a custom sidebar. This makes these items part of the
"Your work" sidebar under a new entry "Security".

Changelog: changed
EE: true