root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2023-08-28 21:10:41 +00:00
parent 672c5fcf46
commit 9a4a8e6be7
483 changed files with 1591 additions and 1333 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Gemfile
View File

@ -481,7 +481,7 @@ group :test do
gem 'shoulda-matchers', '~> 5.1.0', require: false
gem 'email_spec', '~> 2.2.0'
gem 'webmock', '~> 3.18.1'
gem 'webmock', '~> 3.19.0'
gem 'rails-controller-testing'
gem 'concurrent-ruby', '~> 1.1'
gem 'test-prof', '~> 1.2.2'

2
Gemfile.checksum
View File

@ -680,7 +680,7 @@
{"name":"warning","version":"1.3.0","platform":"ruby","checksum":"23695a5d8e50bd5c46068931b529bee0b28e4982cbcefbe77d867800dde8069e"},
{"name":"webauthn","version":"3.0.0","platform":"ruby","checksum":"3f77d422c2a8a4b31e56cf42f83414bd066e0506e9896936e1730262dc4a20e6"},
{"name":"webfinger","version":"1.2.0","platform":"ruby","checksum":"7814ef1c85da47514f65c6e5ca14205fa9ce41ea2a70785e0c872842162852a2"},
{"name":"webmock","version":"3.18.1","platform":"ruby","checksum":"54c955df4ae4bec6181dd266eeec632a1808288c633f9551d81bafb53921d2d7"},
{"name":"webmock","version":"3.19.0","platform":"ruby","checksum":"449ca93acc517a90b35e13c3b652e27b5a24f585800be5dab1f49338e9242314"},
{"name":"webrick","version":"1.8.1","platform":"ruby","checksum":"19411ec6912911fd3df13559110127ea2badd0c035f7762873f58afc803e158f"},
{"name":"websocket","version":"1.2.9","platform":"ruby","checksum":"884b12dee993217795bb5f58acc89c0121c88bdc99df4d1636c0505dca352b36"},
{"name":"websocket-driver","version":"0.7.5","platform":"java","checksum":"fffa83aa188e9ac90e32a385832ec9d26acdf019538e1c7d703f2c8a323b39c8"},

4
Gemfile.lock
View File

@ -1688,7 +1688,7 @@ GEM
webfinger (1.2.0)
activesupport
httpclient (>= 2.4)
webmock (3.18.1)
webmock (3.19.0)
addressable (>= 2.8.0)
crack (>= 0.3.2)
hashdiff (>= 0.4.0, < 2.0.0)
@ -2032,7 +2032,7 @@ DEPENDENCIES
vmstat (~> 2.3.0)
warning (~> 1.3.0)
webauthn (~> 3.0)
webmock (~> 3.18.1)
webmock (~> 3.19.0)
webrick (~> 1.8.1)
wikicloth (= 0.8.1)
yajl-ruby (~> 1.4.3)

22
app/assets/javascripts/repository/components/last_commit.vue
View File

@ -4,7 +4,7 @@ import SafeHtml from '~/vue_shared/directives/safe_html';
import defaultAvatarUrl from 'images/no_avatar.png';
import pathLastCommitQuery from 'shared_queries/repository/path_last_commit.query.graphql';
import { sprintf, s__ } from '~/locale';
import CiIcon from '~/vue_shared/components/ci_icon.vue';
import CiBadgeLink from '~/vue_shared/components/ci_badge_link.vue';
import ClipboardButton from '~/vue_shared/components/clipboard_button.vue';
import TimeagoTooltip from '~/vue_shared/components/time_ago_tooltip.vue';
import UserAvatarLink from '~/vue_shared/components/user_avatar/user_avatar_link.vue';
@ -20,13 +20,13 @@ export default {
UserAvatarLink,
TimeagoTooltip,
ClipboardButton,
CiIcon,
GlButton,
GlButtonGroup,
GlLink,
GlLoadingIcon,
UserAvatarImage,
SignatureBadge,
CiBadgeLink,
},
directives: {
GlTooltip: GlTooltipDirective,
@ -191,18 +191,14 @@ export default {
>
<signature-badge v-if="commit.signature" :signature="commit.signature" />
<div v-if="commit.pipeline" class="ci-status-link">
<gl-link
v-gl-tooltip.left
:href="commit.pipeline.detailedStatus.detailsPath"
:title="statusTitle"
<ci-badge-link
:status="commit.pipeline.detailedStatus"
:details-path="commit.pipeline.detailedStatus.detailsPath"
:aria-label="statusTitle"
badge-size="lg"
:show-text="false"
class="js-commit-pipeline"
>
<ci-icon
:status="commit.pipeline.detailedStatus"
:size="24"
:aria-label="statusTitle"
/>
</gl-link>
/>
</div>
<gl-button-group class="gl-ml-4 js-commit-sha-group">
<gl-button label class="gl-font-monospace" data-testid="last-commit-id-label">{{

6
app/controllers/projects/environments_controller.rb
View File

@ -109,10 +109,8 @@ class Projects::EnvironmentsController < Projects::ApplicationController
job = stop_actions.first if stop_actions&.count == 1
action_or_env_url =
if job.instance_of?(::Ci::Build)
polymorphic_url([project, job])
elsif job.instance_of?(::Ci::Bridge)
project_pipeline_url(project, job.pipeline_id)
if job
project_job_url(project, job)
else
project_environment_url(project, @environment)
end

8
app/controllers/projects/jobs_controller.rb
View File

@ -8,8 +8,8 @@ class Projects::JobsController < Projects::ApplicationController
urgency :low, [:index, :show, :trace, :retry, :play, :cancel, :unschedule, :erase, :raw]
before_action :find_job_as_build, except: [:index, :play, :retry]
before_action :find_job_as_processable, only: [:play, :retry]
before_action :find_job_as_build, except: [:index, :play, :retry, :show]
before_action :find_job_as_processable, only: [:play, :retry, :show]
before_action :authorize_read_build_trace!, only: [:trace, :raw]
before_action :authorize_read_build!
before_action :authorize_update_build!,
@ -38,6 +38,10 @@ class Projects::JobsController < Projects::ApplicationController
end
def show
if @build.instance_of?(::Ci::Bridge)
redirect_to project_pipeline_path(@build.downstream_pipeline.project, @build.downstream_pipeline.id)
end
respond_to do |format|
format.html
format.json do

2
app/mailers/emails/profile.rb
View File

@ -155,7 +155,7 @@ module Emails
@user = user
@email = email
mail_with_locale(to: @user.notification_email_or_default, subject: subject(_("New email address added")))
email_with_layout(to: @user.notification_email_or_default, subject: subject(_("New email address added")))
end
def new_achievement_email(user, achievement)

12
app/models/group.rb
View File

@ -36,10 +36,10 @@ class Group < Namespace
alias_method :members, :group_members
has_many :users, through: :group_members
has_many :owners,
-> { where(members: { access_level: Gitlab::Access::OWNER }) },
through: :all_group_members,
source: :user
has_many :owners, -> {
where(members: { access_level: Gitlab::Access::OWNER })
.allow_cross_joins_across_databases(url: "https://gitlab.com/gitlab-org/gitlab/-/issues/422405")
}, through: :all_group_members, source: :user
has_many :requesters, -> { where.not(requested_at: nil) }, dependent: :destroy, as: :source, class_name: 'GroupMember' # rubocop:disable Cop/ActiveRecordDependent
has_many :namespace_requesters, -> { where.not(requested_at: nil).unscope(where: %i[source_id source_type]) },
@ -341,6 +341,10 @@ class Group < Namespace
end
end
def users
super.loaded? ? super : super.allow_cross_joins_across_databases(url: "https://gitlab.com/gitlab-org/gitlab/-/issues/422405")
end
# Overrides notification_settings has_many association
# This allows to apply notification settings from parent groups
# to child groups and projects.

3
app/models/project.rb
View File

@ -338,7 +338,8 @@ class Project < ApplicationRecord
primary_key: :project_namespace_id, foreign_key: :member_namespace_id, inverse_of: :project,
class_name: 'ProjectMember'
has_many :users, through: :project_members
has_many :users, -> { allow_cross_joins_across_databases(url: "https://gitlab.com/gitlab-org/gitlab/-/issues/422405") },
through: :project_members
has_many :project_callouts, class_name: 'Users::ProjectCallout', foreign_key: :project_id

1
app/models/project_team.rb
View File

@ -80,6 +80,7 @@ class ProjectTeam
# so we filter out only members of project or project's group
def members_in_project_and_ancestors
members.where(id: member_user_ids)
.allow_cross_joins_across_databases(url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/422405')
end
def members_with_access_levels(access_levels = [])

5
app/services/groups/destroy_service.rb
View File

@ -83,7 +83,10 @@ module Groups
# rubocop:disable CodeReuse/ActiveRecord
def destroy_group_bots
bot_ids = group.members_and_requesters.joins(:user).merge(User.project_bot).pluck(:user_id)
bot_ids = group.members_and_requesters.joins(:user)
.merge(User.project_bot)
.allow_cross_joins_across_databases(url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/422405')
.pluck(:user_id)
current_user_id = current_user.id
group.run_after_commit do

4
app/services/merge_requests/create_ref_service.rb
View File

@ -25,9 +25,7 @@ module MergeRequests
source_sha = initial_source_sha # the SHA to be the merged result of the source (minus the merge commit)
expected_old_oid = "" # the SHA we expect target_ref to be at prior to an update (an optimistic lock)
# TODO: Update this message with the removal of FF merge_trains_create_ref_service and update tests
# This is for compatibility with MergeToRefService during the rollout.
return ServiceResponse.error(message: '3:Invalid merge source') unless first_parent_sha.present?
return ServiceResponse.error(message: 'Invalid merge source') unless first_parent_sha.present?
commit_sha, source_sha, expected_old_oid = maybe_squash!(commit_sha, source_sha, expected_old_oid)
commit_sha, source_sha, expected_old_oid = maybe_rebase!(commit_sha, source_sha, expected_old_oid)

6
app/services/projects/destroy_service.rb
View File

@ -255,7 +255,11 @@ module Projects
# We need to remove them when a project is deleted
# rubocop: disable CodeReuse/ActiveRecord
def destroy_project_bots!
project.members.includes(:user).references(:user).merge(User.project_bot).each do |member|
members = project.members
.allow_cross_joins_across_databases(url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/422405')
.includes(:user).references(:user).merge(User.project_bot)
members.each do |member|
Users::DestroyService.new(current_user).execute(member.user, skip_authorization: true)
end
end

0
app/views/notify/new_email_address_added_email.haml → app/views/notify/new_email_address_added_email.html.haml
View File

0
app/views/notify/new_email_address_added_email.erb → app/views/notify/new_email_address_added_email.text.erb
View File

8
config/feature_flags/development/merge_trains_create_ref_service.yml
View File

@ -1,8 +0,0 @@
---
name: merge_trains_create_ref_service
introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127531
rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/420161
milestone: '16.3'
type: development
group: group::pipeline execution
default_enabled: false

6
db/docs/batched_background_migrations/backfill_nuget_normalized_version.yml Normal file
View File

@ -0,0 +1,6 @@
---
migration_job_name: BackfillNugetNormalizedVersion
description: Introduce a batched background migration to backfill the normalized_version column in packages_nuget_metadata table.
feature_category: package_registry
introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/128675
milestone: 16.4

2
db/docs/members.yml
View File

@ -10,4 +10,4 @@ feature_categories:
description: Stores members per namespace
introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/commit/3503b504eabf95487fc3fb49df953a7d694da4fe
milestone: '7.4'
gitlab_schema: gitlab_main
gitlab_schema: gitlab_main_cell

25
db/post_migrate/20230811103457_queue_backfill_nuget_normalized_version.rb Normal file
View File

@ -0,0 +1,25 @@
# frozen_string_literal: true
class QueueBackfillNugetNormalizedVersion < Gitlab::Database::Migration[2.1]
restrict_gitlab_migration gitlab_schema: :gitlab_main
MIGRATION = "BackfillNugetNormalizedVersion"
DELAY_INTERVAL = 2.minutes
BATCH_SIZE = 6000
SUB_BATCH_SIZE = 250
def up
queue_batched_background_migration(
MIGRATION,
:packages_nuget_metadata,
:package_id,
job_interval: DELAY_INTERVAL,
batch_size: BATCH_SIZE,
sub_batch_size: SUB_BATCH_SIZE
)
end
def down
delete_batched_background_migration(MIGRATION, :packages_nuget_metadata, :package_id, [])
end
end

17
db/post_migrate/20230818034041_prepare_removal_index_success_deployments_on_cluster_id_and_environment_id.rb Normal file
View File

@ -0,0 +1,17 @@
# frozen_string_literal: true
# See https://docs.gitlab.com/ee/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class PrepareRemovalIndexSuccessDeploymentsOnClusterIdAndEnvironmentId < Gitlab::Database::Migration[2.1]
INDEX_NAME = 'index_successful_deployments_on_cluster_id_and_environment_id'
# TODO: Index to be destroyed synchronously in https://gitlab.com/gitlab-org/gitlab/-/issues/402514
def up
prepare_async_index_removal :deployments, %i[cluster_id environment_id], name: INDEX_NAME
end
def down
unprepare_async_index :deployments, %i[cluster_id environment_id], name: INDEX_NAME
end
end

1
db/schema_migrations/20230811103457 Normal file
View File

@ -0,0 +1 @@
6c252953fc80ec7618d2012c77064541ba522f77f7573130ca39ca7d915ae483

1
db/schema_migrations/20230818034041 Normal file
View File

@ -0,0 +1 @@
4b27c841210115277f4d49efc56ac834a7ba8b2afb351e0df45443f14cc01484

36
doc/administration/admin_area.md
View File

@ -10,7 +10,7 @@ type: reference
The Admin Area provides a web UI to manage and configure features of GitLab
self-managed instances. If you are an administrator,to access the Admin Area:
- In GitLab 16.1 and later: on the left sidebar, expand the top-most chevron (**{chevron-down}**), then select **Admin Area**.
- In GitLab 16.1 and later: on the left sidebar, select **Search or go to**, then select **Admin Area**.
- In GitLab 16.0 and earlier: on the top bar, select **Main menu > Admin**.
NOTE:
@ -22,7 +22,7 @@ You can administer all projects in the GitLab instance from the Admin Area's Pro
To access the Projects page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Projects**.
1. Select the **All**, **Private**, **Internal**, or **Public** tab to list only
@ -74,7 +74,7 @@ You can combine the filter options. For example, to list only public projects wi
You can administer all users in the GitLab instance from the Admin Area's Users page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
@ -119,7 +119,7 @@ This allows the administrator to "see what the user sees," and take actions on b
You can impersonate a user in the following ways:
- Through the UI:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Users**.
1. From the list of users, select a user.
@ -138,7 +138,7 @@ By default, impersonation is enabled. GitLab can be configured to [disable imper
When using authentication providers, administrators can see the identities for a user:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. From the list of users, select a user.
@ -185,7 +185,7 @@ GitLab billing is based on the number of [**Billable users**](../subscriptions/s
You must be an administrator to manually add emails to users:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Locate the user and select them.
@ -202,7 +202,7 @@ The [Cohorts](user_cohorts.md) tab displays the monthly cohorts of new users and
By default, users can create groups. To prevent a user from creating a top level group:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Locate the user and select them.
@ -218,7 +218,7 @@ You can administer all groups in the GitLab instance from the Admin Area's Group
To access the Groups page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Groups**.
@ -244,7 +244,7 @@ To [Create a new group](../user/group/index.md#create-a-group) select **New grou
To view all topics in the GitLab instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
@ -252,7 +252,7 @@ For each topic, the page displays its name and the number of projects labeled wi
### Search for topics
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
1. In the search box, enter your search criteria.
@ -262,7 +262,7 @@ For each topic, the page displays its name and the number of projects labeled wi
To create a topic:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
1. Select **New topic**.
@ -282,7 +282,7 @@ Do not include sensitive information in the name of a topic.
You can edit a topic's name, title, description, and avatar at any time.
To edit a topic:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
1. Select **Edit** in that topic's row.
@ -294,7 +294,7 @@ To edit a topic:
If you no longer need a topic, you can permanently remove it.
To remove a topic:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
1. To remove a topic, select **Remove** in that topic's row.
@ -307,7 +307,7 @@ After a merged topic is deleted, you cannot restore it.
To merge topics:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Topics**.
1. Select **Merge topics**.
@ -322,7 +322,7 @@ page. For more details, see [Gitaly](gitaly/index.md).
To access the **Gitaly Servers** page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Gitaly Servers**.
@ -347,7 +347,7 @@ You can administer all runners in the GitLab instance from the Admin Area's **Ru
To access the **Runners** page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Runners**.
@ -374,7 +374,7 @@ You can also filter runners by status, type, and tag. To filter:
You can delete multiple runners at the same time.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Runners**.
1. To the left of the runners you want to delete, select the checkbox.
@ -405,7 +405,7 @@ You can administer all jobs in the GitLab instance from the Admin Area's Jobs pa
To access the Jobs page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **CI/CD > Jobs**. All jobs are listed, in descending order of job ID.
1. Select the **All** tab to list all jobs. Select the **Pending**, **Running**, or **Finished**

2
doc/administration/analytics/dev_ops_reports.md
View File

@ -12,7 +12,7 @@ from planning to monitoring.
To see DevOps Reports:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Analytics > DevOps Reports**.

2
doc/administration/analytics/index.md
View File

@ -18,7 +18,7 @@ Prerequisite:
To view instance-level analytics:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Analytics**, then one of the available analytics:

2
doc/administration/analytics/usage_trends.md
View File

@ -19,7 +19,7 @@ Usage Trends data refreshes daily.
To view Usage Trends:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Analytics > Usage Trends**.

4
doc/administration/appearance.md
View File

@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
Several options are available for customizing the appearance of a self-managed instance
of GitLab. To access these settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Appearance**.
@ -83,7 +83,7 @@ description, and icon.
To configure the PWA settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Appearance**.
1. Scroll to the **Progressive Web App (PWA)** section.

40
doc/administration/audit_event_streaming/index.md
View File

@ -46,7 +46,7 @@ Prerequisites:
To add streaming destinations to a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select **Add streaming destination** and select **HTTP endpoint** to show the section for adding destinations.
@ -66,7 +66,7 @@ Prerequisites:
To list the streaming destinations for a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select the stream to expand it and see all the custom HTTP headers.
@ -79,7 +79,7 @@ Prerequisites:
To update a streaming destination's name:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select the stream to expand.
@ -88,7 +88,7 @@ To update a streaming destination's name:
To update a streaming destination's custom HTTP headers:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select the stream to expand.
@ -111,7 +111,7 @@ Prerequisites:
To delete a streaming destination:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -120,7 +120,7 @@ To delete a streaming destination:
To delete only the custom HTTP headers for a streaming destination:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -145,7 +145,7 @@ Prerequisites:
To list streaming destinations and see the verification tokens:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select the **Streams**.
1. Select the stream to expand.
@ -162,7 +162,7 @@ A streaming destination that has an event type filter set has a **filtered** (**
To update a streaming destination's event filters:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -203,7 +203,7 @@ Prerequisites:
To add Google Cloud Logging streaming destinations to a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select **Add streaming destination** and select **Google Cloud Logging** to show the section for adding destinations.
@ -218,7 +218,7 @@ Prerequisites:
To list Google Cloud Logging streaming destinations for a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select the Google Cloud Logging stream to expand and see all the fields.
@ -231,7 +231,7 @@ Prerequisites:
To update Google Cloud Logging streaming destinations to a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select **Streams** tab.
1. Select the Google Cloud Logging stream to expand.
@ -246,7 +246,7 @@ Prerequisites:
To delete Google Cloud Logging streaming destinations to a top-level group:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Secure > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the Google Cloud Logging stream to expand.
@ -274,7 +274,7 @@ Prerequisites:
To add a streaming destination for an instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select **Streams** tab.
@ -295,7 +295,7 @@ Prerequisites:
To list the streaming destinations for an instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select **Streams** tab.
@ -309,7 +309,7 @@ Prerequisites:
To update a instance streaming destination's name:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select **Streams** tab.
@ -319,7 +319,7 @@ To update a instance streaming destination's name:
To update a instance streaming destination's custom HTTP headers:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select **Streams** tab.
@ -343,7 +343,7 @@ Prerequisites:
To delete the streaming destinations for an instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select the **Streams** tab.
@ -353,7 +353,7 @@ To delete the streaming destinations for an instance:
To delete only the custom HTTP headers for a streaming destination:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select the **Streams** tab.
@ -384,7 +384,7 @@ Prerequisites:
To list streaming destinations for an instance and see the verification tokens:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select the **Streams** tab.
@ -401,7 +401,7 @@ A streaming destination that has an event type filter set has a **filtered** (**
To update a streaming destination's event filters:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. On the main area, select the **Streams** tab.

4
doc/administration/audit_events.md
View File

@ -69,7 +69,7 @@ You can view audit events from user actions across an entire GitLab instance.
To view instance audit events:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
@ -82,7 +82,7 @@ To view instance audit events:
You can export the current view (including filters) of your instance audit events as a CSV file. To export the instance
audit events to CSV:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Audit Events**.
1. Select the available search [filters](#filter-audit-events).

2
doc/administration/auditor_users.md
View File

@ -31,7 +31,7 @@ To create a new user account with auditor access (or change an existing user):
To create a user account with auditor access:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Users**.
1. Create a new user or edit an existing one. Set **Access Level** to **Auditor**.

6
doc/administration/auth/ldap/ldap-troubleshooting.md
View File

@ -167,7 +167,7 @@ may see the following message: `Access denied for your LDAP account`.
We have a workaround, based on toggling the access level of affected users:
1. As an administrator, on the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. As an administrator, on the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Users**.
1. Select the name of the affected user.
@ -225,7 +225,7 @@ field contains no data:
To resolve this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, go to **Settings > General**.
1. Expand both of the following:
@ -369,7 +369,7 @@ things to debug the situation.
- Ensure the correct [LDAP group link is added to the GitLab group](ldap_synchronization.md#add-group-links).
- Check that the user has an LDAP identity:
1. Sign in to GitLab as an administrator user.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Users**.
1. Search for the user.

4
doc/administration/auth/ldap/ldap_synchronization.md
View File

@ -501,7 +501,7 @@ When global group memberships lock is enabled:
To enable global group memberships lock:
1. [Configure LDAP](index.md#configure-ldap).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand the **Visibility and access controls** section.
@ -514,7 +514,7 @@ By default, group members with the Owner role can manage [LDAP group synchroniza
GitLab administrators can remove this permission from group Owners:
1. [Configure LDAP](index.md#configure-ldap).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Visibility and access controls**.

4
doc/administration/backup_restore/index.md
View File

@ -107,7 +107,7 @@ To prepare the new server:
```
1. Disable periodic background jobs:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. Under the Sidekiq dashboard, select **Cron** tab and then
@ -188,7 +188,7 @@ To prepare the new server:
1. [Restore the GitLab backup](#restore-gitlab).
1. Verify that the Redis database restored correctly:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. Under the Sidekiq dashboard, verify that the numbers

6
doc/administration/broadcast_messages.md
View File

@ -57,7 +57,7 @@ To display messages to users on your GitLab instance, add a broadcast message.
To add a broadcast message:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Messages**.
1. Select **Add new message**.
@ -86,7 +86,7 @@ If you must make changes to a broadcast message, you can edit it.
To edit a broadcast message:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Messages**.
1. From the list of broadcast messages, select the edit button for the message.
@ -101,7 +101,7 @@ You can delete a broadcast message while it's active.
To delete a broadcast message:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Messages**.
1. From the list of broadcast messages, select the delete button for the message.

2
doc/administration/credentials_inventory.md
View File

@ -32,7 +32,7 @@ You can also [revoke](#revoke-a-users-personal-access-token) and [delete](#delet
To access the Credentials inventory:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Credentials**.

2
doc/administration/custom_project_templates.md
View File

@ -33,7 +33,7 @@ To set project templates at the group level, see [Custom group-level project tem
To select the group to use as the source for the project templates:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Templates**.
1. Expand **Custom project templates**.

2
doc/administration/diff_limits.md
View File

@ -33,7 +33,7 @@ set values are presented as **Too large** are cannot be expanded in the UI.
To configure these values:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Diff limits**.

2
doc/administration/email_from_gitlab.md
View File

@ -22,7 +22,7 @@ For information about email notifications originating from GitLab, read
## Sending emails to users from GitLab
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select **Send email to users**.

4
doc/administration/external_users.md
View File

@ -40,7 +40,7 @@ An administrator can flag a user as external by either of the following methods:
- [Through the API](../api/users.md#user-modification).
- Using the GitLab UI:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Users** to create a new user or edit an existing one.
There, you can find the option to flag the user as external.
@ -56,7 +56,7 @@ Additionally, users can be set as external users using:
By default, new users are not set as external users. This behavior can be changed
by an administrator:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.

8
doc/administration/geo/disaster_recovery/background_verification.md
View File

@ -49,7 +49,7 @@ Feature.enable('geo_repository_verification')
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Expand **Verification information** tab for that site to view automatic checksumming
@ -60,7 +60,7 @@ On the **primary** site:
On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Expand **Verification information** tab for that site to view automatic checksumming
@ -89,7 +89,7 @@ increase load and vice versa.
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **Edit** for the **primary** site to customize the minimum
@ -138,7 +138,7 @@ sudo gitlab-rake geo:verification:wiki:reset
If the **primary** and **secondary** sites have a checksum verification mismatch, the cause may not be apparent. To find the cause of a checksum mismatch:
1. On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Projects**.
1. Find the project that you want to check the checksum differences and

10
doc/administration/geo/disaster_recovery/planned_failover.md
View File

@ -154,7 +154,7 @@ ensure these processes are close to 100% as possible during active use.
On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
Replicated objects (shown in green) should be close to 100%,
@ -183,7 +183,7 @@ This [content was moved to another location](background_verification.md).
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Messages**.
1. Add a message notifying users on the maintenance window.
@ -197,7 +197,7 @@ To ensure that all data is replicated to a secondary site, updates (write reques
be disabled on the **primary** site:
1. Enable [maintenance mode](../../maintenance_mode/index.md) on the **primary** site.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Cron**.
@ -211,7 +211,7 @@ be disabled on the **primary** site:
1. If you are manually replicating any data not managed by Geo, trigger the
final replication process now.
1. On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
@ -227,7 +227,7 @@ be disabled on the **primary** site:
- The Geo log cursor is up to date (0 events behind).
1. On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`

6
doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md
View File

@ -65,7 +65,7 @@ promote a Geo replica and perform a failover.
On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites** to see its status.
Replicated objects (shown in green) should be close to 100%,
@ -105,7 +105,7 @@ follow these steps to avoid unnecessary data loss:
[data not managed by Geo](../../replication/datatypes.md#limitations-on-replicationverification),
trigger the final replication process now.
1. On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
@ -121,7 +121,7 @@ follow these steps to avoid unnecessary data loss:
- The Geo log cursor is up to date (0 events behind).
1. On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`

6
doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md
View File

@ -115,7 +115,7 @@ follow these steps to avoid unnecessary data loss:
connection.
1. On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Cron**.
@ -134,7 +134,7 @@ follow these steps to avoid unnecessary data loss:
[data not managed by Geo](../../replication/datatypes.md#limitations-on-replicationverification),
trigger the final replication process now.
1. On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
@ -150,7 +150,7 @@ follow these steps to avoid unnecessary data loss:
- The Geo log cursor is up to date (0 events behind).
1. On the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`

2
doc/administration/geo/index.md
View File

@ -161,7 +161,7 @@ public URL of the primary site is used.
To update the internal URL of the primary Geo site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **Edit** on the primary site.

6
doc/administration/geo/replication/configuration.md
View File

@ -217,7 +217,7 @@ In the following steps, replace `<ssh_host_key_path>` with the one you're using:
```
1. Navigate to the Primary Node GitLab Instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **Add site**.
@ -327,7 +327,7 @@ method to be enabled. This is enabled by default, but if converting an existing
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Visibility and access controls**.
@ -341,7 +341,7 @@ On the **primary** site:
You can sign in to the **secondary** site with the same credentials you used with
the **primary** site. After you sign in:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Verify that it's correctly identified as a **secondary** Geo site, and that

2
doc/administration/geo/replication/container_registry.md
View File

@ -166,7 +166,7 @@ For each application and Sidekiq node on the **secondary** site:
To verify Container Registry replication is working, on the **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Nodes**.
The initial replication, or "backfill", is probably still in progress.

2
doc/administration/geo/replication/disable_geo.md
View File

@ -36,7 +36,7 @@ to do that.
To remove the **primary** site:
1. [Remove all secondary Geo sites](remove_geo_site.md)
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Nodes**.
1. Select **Remove** for the **primary** node.

2
doc/administration/geo/replication/object_storage.md
View File

@ -41,7 +41,7 @@ whether they are stored on the local file system or in object storage.
To enable GitLab replication:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Nodes**.
1. Select **Edit** on the **secondary** site.

2
doc/administration/geo/replication/remove_geo_site.md
View File

@ -9,7 +9,7 @@ type: howto
**Secondary** sites can be removed from the Geo cluster using the Geo administration page of the **primary** site. To remove a **secondary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Nodes**.
1. For the **secondary** site you want to remove, select **Remove**.

6
doc/administration/geo/replication/troubleshooting.md
View File

@ -27,7 +27,7 @@ Before attempting more advanced troubleshooting:
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
@ -1346,7 +1346,7 @@ If you have updated the value of `external_url` in `/etc/gitlab/gitlab.rb` for t
In this case, make sure to update the changed URL on all your sites:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Change the URL and save the change.
@ -1452,7 +1452,7 @@ site's URL matches its external URL.
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Find the affected **secondary** site and select **Edit**.

2
doc/administration/geo/replication/tuning.md
View File

@ -14,7 +14,7 @@ in the background.
On the **primary** site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **Edit** of the secondary site you want to tune.

4
doc/administration/geo_sites.md
View File

@ -11,7 +11,7 @@ You can configure various settings for GitLab Geo sites. For more information, s
On either the primary or secondary site:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Geo > Sites**.
@ -72,7 +72,7 @@ the primary uses the secondary's internal URL to contact it directly.
The internal URL defaults to external URL. To change it:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Geo > Sites**.
1. Select **Edit** on the site you want to customize.

2
doc/administration/gitaly/praefect.md
View File

@ -1337,7 +1337,7 @@ Particular attention should be shown to:
1. Check that the Praefect storage is configured to store new repositories:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository**.
1. Expand the **Repository storage** section.

2
doc/administration/gitaly/troubleshooting.md
View File

@ -20,7 +20,7 @@ and our advice on [parsing the `gitaly/current` file](../logs/log_parsing.md#par
When using standalone Gitaly servers, you must make sure they are the same version
as GitLab to ensure full compatibility:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Gitaly Servers**.
1. Confirm all Gitaly servers indicate that they are up to date.

6
doc/administration/housekeeping.md
View File

@ -76,7 +76,7 @@ frequently.
You can change how often Gitaly is asked to optimize a repository.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository**.
1. Expand **Repository maintenance**.
@ -109,7 +109,7 @@ housekeeping tasks. The manual trigger can be useful when either:
To trigger housekeeping tasks manually:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
1. On the left sidebar, select **Search or go to** and find your project.
1. On the left sidebar, select **Settings > General**.
1. Expand **Advanced**.
1. Select **Run housekeeping**.
@ -136,7 +136,7 @@ reduce the likelihood of such race conditions.
To trigger a manual prune of unreachable objects:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
1. On the left sidebar, select **Search or go to** and find your project.
1. On the left sidebar, select **Settings > General**.
1. Expand **Advanced**.
1. Select **Run housekeeping**.

2
doc/administration/inactive_project_deletion.md
View File

@ -23,7 +23,7 @@ For the default setting on GitLab.com, see the [GitLab.com settings page](../use
To configure deletion of inactive projects:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository**.
1. Expand **Repository maintenance**.

2
doc/administration/integration/diagrams_net.md
View File

@ -43,7 +43,7 @@ For more information, see [Run your own diagrams.net server with Docker](https:/
## Enable Diagrams.net integration
1. Sign in to GitLab as an [Administrator](../../user/permissions.md) user.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Diagrams.net**.

2
doc/administration/integration/kroki.md
View File

@ -61,7 +61,7 @@ read the [Kroki installation](https://docs.kroki.io/kroki/setup/install/#_images
You need to enable Kroki integration from Settings under Admin Area.
To do that, sign in with an administrator account and follow these steps:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Go to **Settings > General**.
1. Expand the **Kroki** section.

2
doc/administration/integration/mailgun.md
View File

@ -43,7 +43,7 @@ After configuring your Mailgun domain for the webhook endpoints,
you're ready to enable the Mailgun integration:
1. Sign in to GitLab as an [Administrator](../../user/permissions.md) user.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, go to **Settings > General** and expand the **Mailgun** section.
1. Select the **Enable Mailgun** checkbox.

2
doc/administration/integration/plantuml.md
View File

@ -317,7 +317,7 @@ stop;
After configuring your local PlantUML server, you're ready to enable the PlantUML integration:
1. Sign in to GitLab as an [Administrator](../../user/permissions.md) user.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, go to **Settings > General** and expand the **PlantUML** section.
1. Select the **Enable PlantUML** checkbox.

2
doc/administration/integration/terminal.md
View File

@ -112,7 +112,7 @@ they receive a `Connection failed` message.
By default, terminal sessions do not expire. To limit the terminal session
lifetime in your GitLab instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Web terminal**.
1. Set a `max session time`.

2
doc/administration/license.md
View File

@ -28,7 +28,7 @@ To activate your instance with an activation code:
- Your subscription confirmation email.
- The [Customers Portal](https://customers.gitlab.com/customers/sign_in), on the **Manage Purchases** page.
1. Sign in to your GitLab self-managed instance.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Subscription**.
1. Paste the activation code in **Activation code**.

6
doc/administration/license_file.md
View File

@ -18,7 +18,7 @@ link to the **Add license** page should be displayed.
Otherwise, to add your license:
1. Sign in to GitLab as an administrator.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. In the **Add License** area, add a license by either uploading the file or entering the key.
@ -96,7 +96,7 @@ To go back to Free features, [delete all expired licenses](#remove-a-license).
To remove a license from a self-managed instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Subscription**.
1. Select **Remove license**.
@ -107,7 +107,7 @@ Repeat these steps to remove all licenses, including those applied in the past.
To view your license details:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Subscription**.

6
doc/administration/maintenance_mode/index.md
View File

@ -21,7 +21,7 @@ Maintenance Mode allows most external actions that do not change internal state.
Enable Maintenance Mode as an administrator in one of these ways:
- **Web UI**:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Maintenance Mode**, and toggle **Enable Maintenance Mode**.
@ -46,7 +46,7 @@ Enable Maintenance Mode as an administrator in one of these ways:
Disable Maintenance Mode in one of three ways:
- **Web UI**:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Maintenance Mode**, and toggle **Enable Maintenance Mode**.
@ -181,7 +181,7 @@ you should disable all cron jobs except for those related to Geo.
To monitor queues and disable jobs:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. In the Sidekiq dashboard, select **Cron** and disable jobs individually or all at once by selecting **Disable All**.

2
doc/administration/merge_requests_approvals.md
View File

@ -19,7 +19,7 @@ and can no longer be changed:
To enable merge request approval settings for an instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Push Rules**.
1. Expand **Merge request approvals**.

24
doc/administration/moderate_users.md
View File

@ -42,7 +42,7 @@ sign in.
To view user sign ups pending approval:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Pending approval** tab.
@ -53,7 +53,7 @@ A user sign up pending approval can be approved or rejected from the Admin Area.
To approve or reject a user sign up:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Pending approval** tab.
@ -79,7 +79,7 @@ administrators can choose to block the user.
Users can be blocked [via an abuse report](../administration/review_abuse_reports.md#blocking-users),
by removing them in LDAP, or directly from the Admin Area. To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Optional. Select a user.
@ -103,7 +103,7 @@ Users can also be blocked using the [GitLab API](../api/users.md#block-user).
A blocked user can be unblocked from the Admin Area. To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Blocked** tab.
@ -120,7 +120,7 @@ Users can also be unblocked using the [GitLab API](../api/users.md#unblock-user)
The unblock option may be unavailable for LDAP users. To enable the unblock option,
the LDAP identity first needs to be deleted:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Blocked** tab.
@ -160,7 +160,7 @@ Users are notified about account deactivation if
A user can be deactivated from the Admin Area. To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Optional. Select a user.
@ -189,7 +189,7 @@ Administrators can enable automatic deactivation of users who either:
To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -240,7 +240,7 @@ A deactivated user can be activated from the Admin Area.
To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Deactivated** tab.
@ -271,7 +271,7 @@ To block a user and hide their contributions, administrators can ban the user.
Users can be banned using the Admin Area. To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Optional. Select a user.
@ -284,7 +284,7 @@ The banned user does not consume a [seat](../subscriptions/self_managed/index.md
A banned user can be unbanned using the Admin Area. To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Banned** tab.
@ -299,7 +299,7 @@ The user's state is set to active and they consume a
Use the Admin Area to delete users.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Banned** tab.
@ -314,7 +314,7 @@ You can only delete a user if there are inherited or direct owners of a group. Y
You can also delete a user and their contributions, such as merge requests, issues, and groups of which they are the only group owner.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Banned** tab.

2
doc/administration/monitoring/performance/gitlab_configuration.md
View File

@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
GitLab Performance Monitoring is disabled by default. To enable it and change any of its
settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Metrics and profiling**
(`/admin/application_settings/metrics_and_profiling`).

2
doc/administration/monitoring/performance/grafana_configuration.md
View File

@ -35,7 +35,7 @@ see the [GitLab Grafana dashboards](https://gitlab.com/gitlab-org/grafana-dashbo
After setting up Grafana, you can enable a link to access it from the
GitLab sidebar:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Metrics and profiling**
and expand **Metrics - Grafana**.

2
doc/administration/monitoring/performance/performance_bar.md
View File

@ -107,7 +107,7 @@ The performance bar is disabled by default for non-administrators. To enable it
for a given group:
1. Sign in as a user with administrator access.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Metrics and profiling**
(`admin/application_settings/metrics_and_profiling`), and expand

2
doc/administration/monitoring/prometheus/gitlab_metrics.md
View File

@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
To enable the GitLab Prometheus metrics:
1. Log in to GitLab as a user with administrator access.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Metrics and profiling**.
1. Find the **Metrics - Prometheus** section, and select **Enable GitLab Prometheus metrics endpoint**.

4
doc/administration/operations/fast_ssh_key_lookup.md
View File

@ -121,7 +121,7 @@ users as long as a large file exists.
To disable writes to the `authorized_keys` file:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Network**.
1. Expand **Performance optimization**.
@ -141,7 +141,7 @@ This overview is brief. Refer to the above instructions for more context.
1. [Rebuild the `authorized_keys` file](../raketasks/maintenance.md#rebuild-authorized_keys-file).
1. Enable writes to the `authorized_keys` file.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Network**.
1. Expand **Performance optimization**.

2
doc/administration/packages/container_registry.md
View File

@ -343,7 +343,7 @@ the Container Registry by themselves, follow the steps below.
In GitLab, tokens for the Container Registry expire every five minutes.
To increase the token duration:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > CI/CD**.
1. Expand **Container Registry**.

16
doc/administration/pages/index.md
View File

@ -406,7 +406,7 @@ domain as a custom domain to their project.
If your user base is private or otherwise trusted, you can disable the
verification requirement:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Pages**.
@ -424,7 +424,7 @@ sites served under a custom domain.
To enable it:
1. Choose an email address on which you want to receive notifications about expiring domains.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Pages**.
@ -478,7 +478,7 @@ pre-existing applications must modify the GitLab Pages OAuth application. Follow
this:
1. Enable [access control](#access-control).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Applications**.
1. Expand **GitLab Pages**.
@ -498,7 +498,7 @@ This can be helpful to restrict information published with Pages websites to the
of your instance only.
To do that:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Pages**.
@ -689,7 +689,7 @@ Prerequisite:
To set the global maximum pages size for a project:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Pages**.
@ -704,7 +704,7 @@ Prerequisite:
To set the maximum size of each GitLab Pages site in a group, overriding the inherited setting:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
1. On the left sidebar, select **Search or go to** and find your group.
1. On the left sidebar, select **Settings > General**.
1. Expand **Pages**.
1. Enter a value under **Maximum size** in MB.
@ -718,7 +718,7 @@ Prerequisite:
To set the maximum size of GitLab Pages site in a project, overriding the inherited setting:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
1. On the left sidebar, select **Search or go to** and find your project.
1. On the left sidebar, select **Deploy > Pages**.
1. In **Maximum size of pages**, enter the size in MB.
1. Select **Save changes**.
@ -731,7 +731,7 @@ Prerequisite:
To set the maximum number of GitLab Pages custom domains for a project:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**, and expand **Pages**.
1. Enter a value for **Maximum number of custom domains per project**. Use `0` for unlimited domains.

2
doc/administration/pages/source.md
View File

@ -479,7 +479,7 @@ The default for the maximum size of unpacked archives per project is 100 MB.
To change this value:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Pages**.

4
doc/administration/pages/troubleshooting.md
View File

@ -170,7 +170,7 @@ Upgrading to an [officially supported operating system](https://about.gitlab.com
This problem comes from the permissions of the GitLab Pages OAuth application. To fix it:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Applications > GitLab Pages**.
1. Edit the application.
@ -214,7 +214,7 @@ You may see this error if `pages_external_url` was updated at some point of time
1. Check the [System OAuth application](../../integration/oauth_provider.md#create-an-instance-wide-application):
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Applications** and then **Add new application**.
1. Ensure the **Callback URL/Redirect URI** is using the protocol (HTTP or HTTPS) that

2
doc/administration/polling.md
View File

@ -26,7 +26,7 @@ The default value (`1`) is recommended for the majority of GitLab installations.
To adjust the polling interval multiplier:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Preferences**.
1. Expand **Polling interval multiplier**.

2
doc/administration/raketasks/storage.md
View File

@ -109,7 +109,7 @@ sudo gitlab-rake gitlab:storage:migrate_to_hashed ID_FROM=50 ID_TO=100
To monitor the progress in GitLab:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Monitoring > Background Jobs**.
1. Watch how long the `hashed_storage:hashed_storage_project_migrate` queue

4
doc/administration/reporting/git_abuse_rate_limit.md
View File

@ -21,7 +21,7 @@ GitLab team members can view more information in this confidential epic:
## Configure Git abuse rate limiting
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Reporting**.
1. Expand **Git abuse rate limit**.
@ -41,7 +41,7 @@ If automatic banning is enabled, an email notification is sent when a user is ab
## Unban a user
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Users**.
1. Select the **Banned** tab and search for the account you want to unban.

2
doc/administration/reporting/ip_addr_restrictions.md
View File

@ -19,7 +19,7 @@ unique IP addresses. Therefore, the IP addresses per user limit should take into
## Configure IP address restrictions
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Reporting**.
1. Expand **Spam and Anti-bot Protection**.

2
doc/administration/reporting/spamcheck.md
View File

@ -40,7 +40,7 @@ Spamcheck is only available for package-based installations:
## Configure GitLab to use Spamcheck
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Reporting**.
1. Expand **Spam and Anti-bot Protection**.

6
doc/administration/repository_checks.md
View File

@ -20,7 +20,7 @@ committed to a repository. GitLab administrators can:
To check a project's repository using GitLab UI:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Projects**.
1. Select the project to check.
@ -33,7 +33,7 @@ project page in the Admin Area. If the checks fail, see [what to do](#what-to-do
Instead of checking repositories manually, GitLab can be configured to run the checks periodically:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository** (`/admin/application_settings/repository`).
1. Expand the **Repository maintenance** section.
@ -87,7 +87,7 @@ If a repository check fails, locate the error in the [`repocheck.log` file](logs
If periodic repository checks cause false alarms, you can clear all repository check states:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository** (`/admin/application_settings/repository`).
1. Expand the **Repository maintenance** section.

2
doc/administration/repository_storage_paths.md
View File

@ -26,7 +26,7 @@ For more information on:
After you configure multiple repository storages, you can choose where new repositories are stored:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > Repository** and expand the **Repository storage**
section.

2
doc/administration/repository_storage_types.md
View File

@ -66,7 +66,7 @@ Administrators can look up a project's hashed path from its name or ID using:
To look up a project's hash path in the Admin Area:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Overview > Projects** and select the project.
1. Locate the **Relative path** field. The value is similar to:

4
doc/administration/review_abuse_reports.md
View File

@ -16,7 +16,7 @@ reports in the Admin Area.
To receive notifications of new abuse reports by email:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Reporting**.
1. Expand the **Abuse reports** section.
@ -34,7 +34,7 @@ To find out more about reporting abuse, see
To access abuse reports:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Abuse Reports**.

2
doc/administration/server_hooks.md
View File

@ -71,7 +71,7 @@ If you implemented the server hook code correctly, it should execute when the Gi
To create server hooks for a repository:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Go to **Overview > Projects** and select the project you want to add a server hook to.
1. On the page that appears, locate the value of **Relative path**. This path is where server

42
doc/administration/settings/account_and_limit_settings.md
View File

@ -16,7 +16,7 @@ the [project limits for existing users](#projects-limit-for-a-user).
To configure the maximum number of projects in personal namespaces for new users:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -30,7 +30,7 @@ in their users personal namespace. However, projects can still be created in a g
You can edit a specific user, and change the maximum number of projects this user
can create in their personal namespace:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview** > **Users**.
1. From the list of users, select a user.
@ -44,7 +44,7 @@ can create in their personal namespace:
The maximum file size for attachments in GitLab comments and replies is 100 MB.
To change the maximum attachment size:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -60,7 +60,7 @@ For GitLab.com repository size limits, read [accounts and limit settings](../../
You can change the maximum push size for your instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -81,7 +81,7 @@ Use [Git LFS](../../topics/git/lfs/index.md) to add large files to a repository.
To modify the maximum file size for exports in GitLab:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**, then expand **Account and limit**.
1. Increase or decrease by changing the value in **Maximum export size (MB)**.
@ -92,7 +92,7 @@ To modify the maximum file size for exports in GitLab:
To modify the maximum file size for imports in GitLab:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -115,7 +115,7 @@ You can modify the maximum remote file size for imports from external object sto
To modify the maximum import remote file size:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -129,7 +129,7 @@ You can modify the maximum download file size for imports by direct transfer in
To modify the maximum download file size for imports by direct transfer:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -149,7 +149,7 @@ Decompressed archive size validation failed.
To modify the maximum decompressed file size for imports in GitLab:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -163,7 +163,7 @@ When you [import a project](../../user/project/settings/import_export.md), you c
To modify the maximum decompressed file size for imports in GitLab:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -186,7 +186,7 @@ The default prefix is `glpat-` but administrators can change it.
To change the default global prefix:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -233,7 +233,7 @@ These settings can be found in:
1. Fill in the **Repository size limit (MB)** field in the **Naming, visibility** section.
1. Select **Save changes**.
- GitLab global settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -256,7 +256,7 @@ For details on manually purging files, see [reducing the repository size using G
You can change how long users can remain signed in without activity.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**. The set duration is in **Session duration (minutes)**.
@ -271,7 +271,7 @@ For details, see [cookies used for sign-in](../../user/profile/index.md#cookies-
Users can select the **Remember me** checkbox on sign-in, and their session will remain active for an indefinite period of time when accessed from that specific browser. You can turn off this setting if you need sessions to expire for security or compliance purposes. Turning off this setting will ensure users' sessions expire after the number of minutes of inactivity set when you [customize your session duration](#customize-the-default-session-duration).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -289,7 +289,7 @@ GitLab administrators can choose to customize the session duration (in minutes)
To set a limit on how long these sessions are valid:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -317,7 +317,7 @@ there are no restrictions.
To set a lifetime on how long SSH keys are valid:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -354,7 +354,7 @@ there are no restrictions.
To set a lifetime on how long access tokens are valid:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
@ -377,7 +377,7 @@ To maintain integrity of user details in [Audit Events](../../administration/aud
To do this:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -399,7 +399,7 @@ By default, new users can create top-level groups. GitLab administrators can pre
- The [application setting API](../../api/settings.md#change-application-settings).
- In GitLab 15.4 and earlier, a [configuration file](../../administration/user_settings.md#use-configuration-files-to-prevent-new-users-from-creating-top-level-groups).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -411,7 +411,7 @@ By default, new users can create top-level groups. GitLab administrators can pre
By default, newly created users have a public profile. GitLab administrators can set new users to have a private profile by default:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
@ -424,7 +424,7 @@ By default, newly created users have a public profile. GitLab administrators can
By default, users can delete their own accounts. GitLab administrators can prevent
users from deleting their own accounts:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Account and limit**.

44
doc/administration/settings/continuous_integration.md
View File

@ -15,7 +15,7 @@ job artifacts.
To enable (or disable) [Auto DevOps](../../topics/autodevops/index.md)
for all projects:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Check (or uncheck to disable) the box that says **Default to Auto DevOps pipeline for all projects**.
@ -33,7 +33,7 @@ If you want to disable it for a specific project, you can do so in
You can set all new projects to have the instance's shared runners available by default.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
@ -53,7 +53,7 @@ you can assign that runner to other projects.
To enable a project runner for more than one project:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. From the left sidebar, select **CI/CD > Runners**.
1. Select the runner you want to edit.
@ -67,7 +67,7 @@ To enable a project runner for more than one project:
To display details about the instance's shared runners in all projects'
runner settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
@ -77,7 +77,7 @@ runner settings:
To view the rendered details:
1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group.
1. On the left sidebar, select **Search or go to** and find your project or group.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
@ -97,7 +97,7 @@ The value is in MB and the default is 100 MB per job. To change it at the:
- Instance level:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. On the left sidebar, select **Settings > CI/CD > Continuous Integration and Deployment**.
1. Change the value of **Maximum artifacts size (MB)**.
@ -125,7 +125,7 @@ can be set in the Admin Area of your GitLab instance. The syntax of duration is
described in [`artifacts:expire_in`](../../ci/yaml/index.md#artifactsexpire_in)
and the default value is `30 days`.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Change the value of default expiration time.
@ -157,7 +157,7 @@ If disabled at the instance level, you cannot enable this per-project.
To disable the setting:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
@ -181,7 +181,7 @@ blueprint for more details.
To set the duration for which the jobs are considered as old and expired:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Continuous Integration and Deployment** section.
@ -199,7 +199,7 @@ For the value set for GitLab.com, see [Scheduled job archiving](../../user/gitla
To set all new [CI/CD variables](../../ci/variables/index.md) as
[protected](../../ci/variables/index.md#protect-a-cicd-variable) by default:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Select **Protect CI/CD variables by default**.
@ -211,7 +211,7 @@ To set all new [CI/CD variables](../../ci/variables/index.md) as
The maximum number of [includes](../../ci/yaml/includes.md) per pipeline can be set at the instance level.
The default is `150`.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Change the value of **Maximum includes**.
@ -224,7 +224,7 @@ The default is `150`.
The default CI/CD configuration file and path for new projects can be set in the Admin Area
of your GitLab instance (`.gitlab-ci.yml` if not set):
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Input the new file and path in the **Default CI/CD configuration file** field.
@ -239,7 +239,7 @@ It is also possible to specify a [custom CI/CD configuration file for a specific
You can configure some [CI/CD limits](../../administration/instance_limits.md#cicd-limits)
from the Admin Area:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Continuous Integration and Deployment** section.
@ -263,7 +263,7 @@ walkthrough on how to add one.
To enable or disable the banner:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Select or clear the **Enable pipeline suggestion banner** checkbox.
@ -300,7 +300,7 @@ in the pipeline editor.
To select a CI/CD template for the required pipeline configuration:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Required pipeline configuration** section.
@ -315,7 +315,7 @@ GitLab administrators can disable the forwarding of Maven requests to [Maven Cen
To disable forwarding Maven requests:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
@ -328,7 +328,7 @@ GitLab administrators can disable the forwarding of npm requests to [npmjs.com](
To disable it:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
@ -341,7 +341,7 @@ GitLab administrators can disable the forwarding of PyPI requests to [pypi.org](
To disable it:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
@ -354,7 +354,7 @@ GitLab administrators can adjust the maximum allowed file size for each package
To set the maximum file size:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
@ -375,7 +375,7 @@ By default, all members of a project and group are able to register runners.
To restrict all users in an instance from registering runners:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
@ -398,7 +398,7 @@ GitLab administrators can adjust group permissions to restrict runner registrati
To restrict runner registration by members in a specific group:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Overview > Groups** and find your group.
1. Select **Edit**.
@ -413,7 +413,7 @@ By default, GitLab instances periodically fetch official runner version data fro
To disable your instance fetching this data:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.

2
doc/administration/settings/deprecated_api_rate_limits.md
View File

@ -34,7 +34,7 @@ Prerequisite:
To override the general user and IP rate limits for requests to deprecated API endpoints:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Deprecated API Rate Limits**.

12
doc/administration/settings/email.md
View File

@ -21,7 +21,7 @@ address in the body of the email instead.
To include the author's email address in the email body:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
@ -34,7 +34,7 @@ GitLab can send email in multipart format (HTML and plain text) or plain text on
To enable multipart email:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
@ -50,7 +50,7 @@ This configuration option sets the email hostname for [private commit emails](..
To change the hostname used in private commit emails:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
@ -69,7 +69,7 @@ can be used for legal, auditing, or compliance reasons, for example.
To add additional text to emails:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
@ -82,7 +82,7 @@ GitLab sends email notifications to users when their account has been deactivate
To disable these notifications:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
@ -105,7 +105,7 @@ setting.
To add additional text to deactivation emails:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Email**.

4
doc/administration/settings/external_authorization.md
View File

@ -45,7 +45,7 @@ Alternatively, learn where to install custom certificates by using
The external authorization service can be enabled by an administrator:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **External authorization**.
@ -66,7 +66,7 @@ Prerequisites:
To allow authorization with deploy tokens and keys:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **External authorization**, and:

2
doc/administration/settings/files_api_rate_limits.md
View File

@ -30,7 +30,7 @@ Prerequisite:
To override the general user and IP rate limits for requests to the Repository files API:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Files API Rate Limits**.

2
doc/administration/settings/floc.md
View File

@ -22,7 +22,7 @@ Permissions-Policy: interest-cohort=()
To enable it:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > General**.
1. Expand **Federated Learning of Cohorts (FLoC)**.

2
doc/administration/settings/git_lfs_rate_limits.md
View File

@ -21,7 +21,7 @@ rate limits.
Git LFS rate limits are disabled by default. If enabled and configured, these limits
supersede the [general user and IP rate limits](../settings/user_and_ip_rate_limits.md):
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Git LFS Rate Limits**.

2
doc/administration/settings/gitaly_timeouts.md
View File

@ -11,7 +11,7 @@ configured to make sure that long-running Gitaly calls don't needlessly take up
To access Gitaly timeout settings:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand the **Gitaly timeouts** section.

10
doc/administration/settings/help_page.md
View File

@ -16,7 +16,7 @@ the GitLab sign-in page.
You can add a help message, which is shown at the top of the GitLab `/help` page (for example,
<https://gitlab.com/help>):
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Sign-in and Help page**.
@ -34,7 +34,7 @@ is restricted, `/help` is visible only to authenticated users.
You can add a help message, which is shown on the GitLab sign-in page. The message appears on the sign-in page:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Sign-in and Help page**.
@ -48,7 +48,7 @@ You can now see the message on the sign-in page.
GitLab marketing-related entries are occasionally shown on the Help page. To hide these entries:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Sign-in and Help page**.
@ -62,7 +62,7 @@ You can specify a custom URL to which users are directed when they:
- Select **Support** from the Help dropdown list.
- Select **See our website for help** on the Help page.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Sign-in and Help page**.
@ -77,7 +77,7 @@ You can specify a custom URL to which users are directed when they:
You can redirect all `/help` links to a destination that meets the [necessary requirements](#destination-requirements).
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Expand **Sign-in and Help page**.

2
doc/administration/settings/import_export_rate_limits.md
View File

@ -12,7 +12,7 @@ You can configure the rate limits for imports and exports of projects and groups
To change a rate limit:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Import and export rate limits**.

2
doc/administration/settings/incident_management_rate_limits.md
View File

@ -30,7 +30,7 @@ Requests that exceed the limit are logged into `auth.log`.
To set inbound incident management alert limits:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Incident Management Limits**.

6
doc/administration/settings/index.md
View File

@ -19,7 +19,7 @@ read [GitLab.com settings](../../user/gitlab_com/index.md).
To access the **Admin Area**:
1. Sign in to your GitLab instance as an administrator.
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
## Change the default first day of the week
@ -27,7 +27,7 @@ To access the **Admin Area**:
You can change the [Default first day of the week](../../user/profile/preferences.md)
for the entire GitLab instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Scroll to the **Localization** section, and select your desired first day of the week.
@ -37,7 +37,7 @@ for the entire GitLab instance:
You can change the [Default language](../../user/profile/preferences.md)
for the entire GitLab instance:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Preferences**.
1. Scroll to the **Localization** section, and select your desired default language.

2
doc/administration/settings/instance_template_repository.md
View File

@ -20,7 +20,7 @@ while the project remains secure.
To select a project to serve as the custom template repository:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Templates**.
1. Expand **Templates**

4
doc/administration/settings/package_registry_rate_limits.md
View File

@ -30,7 +30,7 @@ no difference in functionality compared to the general user and IP rate limits.
To enable the unauthenticated request rate limit:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**.
1. Expand **Package registry rate limits**.
@ -45,7 +45,7 @@ To enable the unauthenticated request rate limit:
To enable the authenticated API request rate limit:
1. On the left sidebar, expand the top-most chevron (**{chevron-down}**).
1. On the left sidebar, select **Search or go to**.
1. Select **Admin Area**.
1. Select **Settings > Network**
1. Expand **Package registry rate limits**.

Some files were not shown because too many files have changed in this diff Show More