Co-authored-by: Lysanne Pinto <lpinto@gitlab.com>

Co-authored-by: Lysanne Pinto <lpinto@gitlab.com>

Signed-off-by: Nailia Iskhakova <niskhakova@gitlab.com>

Put milestone numbers in these old images, so we can determine
which ones are in most need of replacement.

This MR introduces an application setting (disabled by default) which
controls the ability to perform user contribution mapping to users with
administrative privileges on the instance.

Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/474963

Co-authored-by: Jon Glassman <jglassman@gitlab.com>

Co-authored-by: Suzanne Selhorn <sselhorn@gitlab.com>

Co-authored-by: Brendan Lynch <blynch@gitlab.com>

With model-identifier field, we'll allow specifying model name.
The model column will be used to set model-family instead.

Let's reflect it in the enum field: support setting a model family
instead of a particular model

Because I think theyre incorrect

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/490915

Cover an edge case that prevents users from deleting a project.

Co-authored-by: Lysanne Pinto <lpinto@gitlab.com>

Captures a few details that had to be explained in https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues/6305

Co-authored-by: Marcel Amirault <mamirault@gitlab.com>

Follow-up to 34560a16 & 89c34dfb

Because that's when licensing changes

A new cgroups configuration parameter called `max_cgroups_per_repo` was
introduced with https://gitlab.com/gitlab-org/gitaly/-/issues/5689. This
parameter allows independent Git processes targeting a single repository
to be distributed across multiple repository cgroups. This enables
stricter limits to be defined for repository cgroups while still
allowing for bursty workloads comprising of independent Git operations
against a single repo.

Add documentation and update the example configuration snippet.

Co-authored-by: Suzanne Selhorn <sselhorn@gitlab.com>

Switch to tables for better clarity and readability