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 2024-07-25 00:07:22 +00:00
parent 92bcd7dce0
commit 5f272aeb3c
247 changed files with 1166 additions and 1317 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

135
app/assets/javascripts/profile/components/user_achievements.vue
View File

@ -8,8 +8,6 @@ import timeagoMixin from '~/vue_shared/mixins/timeago';
import { joinPaths } from '~/lib/utils/url_utility';
import getUserAchievements from './graphql/get_user_achievements.query.graphql';
export const MAX_VISIBLE_ACHIEVEMENTS = 7;
export default {
name: 'UserAchievements',
components: { GlAvatar, GlBadge, GlPopover, GlSprintf },
@ -38,27 +36,25 @@ export default {
},
methods: {
processNodes(nodes) {
return Object.entries(groupBy(nodes, 'achievement.id'))
.slice(0, MAX_VISIBLE_ACHIEVEMENTS)
.map(([id, values]) => {
const {
achievement: { name, avatarUrl, description, namespace },
createdAt,
} = values[0];
const count = values.length;
return {
id: `user-achievement-${id}`,
name,
timeAgo: this.timeFormatted(createdAt),
avatarUrl: avatarUrl || gon.gitlab_logo,
description,
namespace: namespace && {
fullPath: namespace.fullPath,
webUrl: joinPaths(this.rootUrl, namespace.achievementsPath),
},
count,
};
});
return Object.entries(groupBy(nodes, 'achievement.id')).map(([id, values]) => {
const {
achievement: { name, avatarUrl, description, namespace },
createdAt,
} = values[0];
const count = values.length;
return {
id: `user-achievement-${id}`,
name,
timeAgo: this.timeFormatted(createdAt),
avatarUrl: avatarUrl || gon.gitlab_logo,
description,
namespace: namespace && {
fullPath: namespace.fullPath,
webUrl: joinPaths(this.rootUrl, namespace.achievementsPath),
},
count,
};
});
},
achievementAwardedMessage(userAchievement) {
return userAchievement.namespace
@ -85,51 +81,56 @@ export default {
<h2 class="gl-font-base gl-mb-2 gl-mt-4">
{{ $options.i18n.achievementsLabel }}
</h2>
<div
v-for="userAchievement in userAchievements"
:key="userAchievement.id"
class="gl-mr-2 gl-display-inline-block gl-align-top gl-text-center"
data-testid="user-achievement"
>
<gl-avatar
:id="userAchievement.id"
:src="userAchievement.avatarUrl"
:size="32"
tabindex="0"
shape="rect"
class="gl-p-1 gl-border-none"
/>
<br />
<gl-badge v-if="showCountBadge(userAchievement.count)" variant="info">{{
getCountBadge(userAchievement.count)
}}</gl-badge>
<gl-popover :target="userAchievement.id">
<div>
<span class="gl-font-bold">{{ userAchievement.name }}</span>
<gl-badge v-if="showCountBadge(userAchievement.count)" variant="info">{{
getCountBadge(userAchievement.count)
}}</gl-badge>
</div>
<div>
<gl-sprintf :message="achievementAwardedMessage(userAchievement)">
<template #timeAgo>
<span>{{ userAchievement.timeAgo }}</span>
</template>
<template v-if="userAchievement.namespace" #namespace>
<a :href="userAchievement.namespace.webUrl">{{
userAchievement.namespace.fullPath
}}</a>
</template>
</gl-sprintf>
</div>
<div
v-if="userAchievement.description"
class="gl-mt-5"
data-testid="achievement-description"
<div class="gl-flex gl-gap-3 gl-flex-wrap">
<div
v-for="userAchievement in userAchievements"
:key="userAchievement.id"
class="gl-relative"
data-testid="user-achievement"
>
<gl-avatar
:id="userAchievement.id"
:src="userAchievement.avatarUrl"
:size="48"
tabindex="0"
shape="rect"
class="gl-p-1 gl-outline-none"
/>
<br />
<gl-badge
v-if="showCountBadge(userAchievement.count)"
class="gl-absolute gl-left-7 gl-top-7 gl-z-1"
variant="info"
>{{ getCountBadge(userAchievement.count) }}</gl-badge
>
{{ userAchievement.description }}
</div>
</gl-popover>
<gl-popover :target="userAchievement.id">
<div>
<span class="gl-font-bold">{{ userAchievement.name }}</span>
<gl-badge v-if="showCountBadge(userAchievement.count)" variant="info">{{
getCountBadge(userAchievement.count)
}}</gl-badge>
</div>
<div>
<gl-sprintf :message="achievementAwardedMessage(userAchievement)">
<template #timeAgo>
<span>{{ userAchievement.timeAgo }}</span>
</template>
<template v-if="userAchievement.namespace" #namespace>
<a :href="userAchievement.namespace.webUrl">{{
userAchievement.namespace.fullPath
}}</a>
</template>
</gl-sprintf>
</div>
<div
v-if="userAchievement.description"
class="gl-mt-5"
data-testid="achievement-description"
>
{{ userAchievement.description }}
</div>
</gl-popover>
</div>
</div>
</div>
</template>

6
app/assets/javascripts/super_sidebar/super_sidebar_bundle.js
View File

@ -19,7 +19,6 @@ Vue.use(VueApollo);
const getTrialStatusWidgetData = (sidebarData) => {
if (sidebarData.trial_status_widget_data_attrs && sidebarData.trial_status_popover_data_attrs) {
const {
containerId,
trialDaysUsed,
trialDuration,
navIconImagePath,
@ -36,7 +35,6 @@ const getTrialStatusWidgetData = (sidebarData) => {
return {
showTrialStatusWidget: true,
showDuoProTrialStatusWidget: false,
containerId,
trialDaysUsed: Number(trialDaysUsed),
trialDuration: Number(trialDuration),
navIconImagePath,
@ -44,7 +42,6 @@ const getTrialStatusWidgetData = (sidebarData) => {
planName,
plansHref,
daysRemaining,
targetId: containerId,
trialEndDate: new Date(trialEndDate),
trialDiscoverPagePath,
};
@ -55,7 +52,6 @@ const getTrialStatusWidgetData = (sidebarData) => {
sidebarData.duo_pro_trial_status_popover_data_attrs
) {
const {
containerId,
trialDaysUsed,
trialDuration,
percentageComplete,
@ -72,7 +68,6 @@ const getTrialStatusWidgetData = (sidebarData) => {
return {
showDuoProTrialStatusWidget: true,
showTrialStatusWidget: false,
containerId,
trialDaysUsed: Number(trialDaysUsed),
trialDuration: Number(trialDuration),
percentageComplete: Number(percentageComplete),
@ -81,7 +76,6 @@ const getTrialStatusWidgetData = (sidebarData) => {
featureId,
dismissEndpoint,
daysRemaining,
targetId: containerId,
trialEndDate: new Date(trialEndDate),
purchaseNowUrl,
learnAboutButtonUrl: widgetUrl,

6
app/assets/javascripts/vue_shared/components/source_viewer/components/blame_info.vue
View File

@ -21,13 +21,13 @@ export default {
};
</script>
<template>
<div class="blame gl-bg-gray-10 gl-border-r">
<div class="blame-commit gl-border-none!">
<div class="blame gl-border-r gl-bg-gray-10">
<div class="blame-commit !gl-border-none">
<commit-info
v-for="(blame, index) in blameInfo"
:key="index"
:class="{ 'gl-border-t': blame.blameOffset !== '0px' }"
class="gl-display-flex gl-absolute gl-px-3"
class="gl-absolute gl-flex gl-px-3"
:style="{ top: blame.blameOffset }"
:commit="blame.commit"
:span="blame.span"

133
app/assets/javascripts/vue_shared/components/source_viewer/components/chunk.vue
View File

@ -1,65 +1,54 @@
<!-- eslint-disable vue/multi-word-component-names -->
<script>
import { GlIntersectionObserver } from '@gitlab/ui';
import LineHighlighter from '~/blob/line_highlighter';
import ChunkLine from './chunk_line.vue';
import SafeHtml from '~/vue_shared/directives/safe_html';
import { getPageParamValue, getPageSearchString } from '~/blob/utils';
/*
* We only highlight the chunk that is currently visible to the user.
* By making use of the Intersection Observer API we can determine when a chunk becomes visible and highlight it accordingly.
*
* Content that is not visible to the user (i.e. not highlighted) do not need to look nice,
* so by making text transparent and rendering raw (non-highlighted) text,
* the browser spends less resources on painting content that is not immediately relevant.
*
* Why use transparent text as opposed to hiding content entirely?
* 1. If content is hidden entirely, native find text (⌘ + F) won't work.
* 2. When URL contains line numbers, the browser needs to be able to jump to the correct line.
* Content that is not visible to the user (i.e. not highlighted) does not need to look nice,
* so by rendering raw (non-highlighted) text, the browser spends less resources on painting
* content that is not immediately relevant.
* Why use plaintext as opposed to hiding content entirely?
* If content is hidden entirely, native find text (⌘ + F) won't work.
*/
export default {
components: {
ChunkLine,
GlIntersectionObserver,
},
directives: {
SafeHtml,
},
props: {
isFirstChunk: {
isHighlighted: {
type: Boolean,
required: false,
default: false,
required: true,
},
chunkIndex: {
type: Number,
required: false,
default: 0,
},
isHighlighted: {
type: Boolean,
required: true,
},
content: {
rawContent: {
type: String,
required: true,
},
startingFrom: {
type: Number,
required: false,
default: 0,
highlightedContent: {
type: String,
required: true,
},
totalLines: {
type: Number,
required: false,
default: 0,
},
totalChunks: {
startingFrom: {
type: Number,
required: false,
default: 0,
},
language: {
type: String,
required: false,
default: null,
},
blamePath: {
type: String,
required: true,
@ -67,37 +56,26 @@ export default {
},
data() {
return {
isLoading: true,
hasAppeared: false,
};
},
computed: {
lines() {
return this.content.split('\n');
shouldHighlight() {
return Boolean(this.highlightedContent) && (this.hasAppeared || this.isHighlighted);
},
pageSearchString() {
const page = getPageParamValue(this.number);
return getPageSearchString(this.blamePath, page);
},
codeStyling() {
const defaultGutterWidth = 96;
return { marginLeft: `${this.$refs.lineNumbers?.offsetWidth || defaultGutterWidth}px` };
},
},
created() {
if (this.isFirstChunk) {
this.isLoading = false;
return;
}
window.requestIdleCallback(async () => {
this.isLoading = false;
const { hash } = this.$route;
if (hash && this.totalChunks > 0 && this.totalChunks === this.chunkIndex + 1) {
// when the last chunk is loaded scroll to the hash
await this.$nextTick();
const lineHighlighter = new LineHighlighter({ scrollBehavior: 'auto' });
lineHighlighter.highlightHash(hash);
}
});
},
methods: {
handleChunkAppear() {
if (!this.isHighlighted) {
this.$emit('appear', this.chunkIndex);
}
this.hasAppeared = true;
this.$emit('appear');
},
calculateLineNumber(index) {
return this.startingFrom + index + 1;
@ -106,29 +84,38 @@ export default {
};
</script>
<template>
<gl-intersection-observer @appear="handleChunkAppear">
<div v-if="isHighlighted">
<chunk-line
v-for="(line, index) in lines"
<div class="gl-flex">
<div v-if="shouldHighlight" class="gl-absolute gl-flex gl-flex-col">
<div
v-for="(n, index) in totalLines"
:key="index"
:number="calculateLineNumber(index)"
:content="line"
:language="language"
:blame-path="blamePath"
/>
</div>
<div v-else-if="!isLoading" class="gl-display-flex gl-text-transparent">
<div class="gl-display-flex gl-flex-direction-column content-visibility-auto">
<span
v-for="(n, index) in totalLines"
v-once
data-testid="line-numbers"
class="diff-line-num line-links line-numbers gl-border-r gl-z-3 gl-flex !gl-p-0"
>
<a
class="file-line-blame gl-select-none !gl-shadow-none"
data-event-tracking="click_chunk_blame_on_blob_page"
:href="`${blamePath}${pageSearchString}#L${calculateLineNumber(index)}`"
></a>
<a
:id="`L${calculateLineNumber(index)}`"
:key="index"
data-testid="line-number"
v-text="calculateLineNumber(index)"
></span>
class="file-line-num gl-select-none !gl-shadow-none"
:href="`#L${calculateLineNumber(index)}`"
:data-line-number="calculateLineNumber(index)"
>
{{ calculateLineNumber(index) }}
</a>
</div>
<div v-once class="gl-whitespace-pre-wrap!" data-testid="content">{{ content }}</div>
</div>
</gl-intersection-observer>
<div v-else ref="lineNumbers" class="line-numbers gl-mr-3 !gl-p-0 gl-text-transparent">
<!-- Placeholder for line numbers while content is not highlighted -->
</div>
<gl-intersection-observer class="gl-w-full" @appear="handleChunkAppear">
<pre
class="code highlight gl-m-0 gl-w-full !gl-overflow-visible !gl-border-none !gl-p-0 gl-leading-0"
><code v-if="shouldHighlight" v-safe-html="highlightedContent" :style="codeStyling" data-testid="content"></code><code v-else v-once class="line !gl-whitespace-pre-wrap gl-ml-1" data-testid="content" v-text="rawContent"></code></pre>
</gl-intersection-observer>
</div>
</template>

58
app/assets/javascripts/vue_shared/components/source_viewer/components/chunk_line.vue
View File

@ -1,58 +0,0 @@
<script>
import SafeHtml from '~/vue_shared/directives/safe_html';
import { getPageParamValue, getPageSearchString } from '~/blob/utils';
export default {
directives: {
SafeHtml,
},
props: {
number: {
type: Number,
required: true,
},
content: {
type: String,
required: true,
},
language: {
type: String,
required: true,
},
blamePath: {
type: String,
required: true,
},
},
computed: {
pageSearchString() {
const page = getPageParamValue(this.number);
return getPageSearchString(this.blamePath, page);
},
},
};
</script>
<template>
<div class="gl-display-flex">
<div
class="gl-p-0! gl-absolute gl-z-3 diff-line-num gl-border-r gl-display-flex line-links line-numbers"
>
<a
class="gl-select-none !gl-shadow-none file-line-blame -gl-mx-2 gl-flex-grow-1"
:href="`${blamePath}${pageSearchString}#L${number}`"
></a>
<a
:id="`L${number}`"
class="gl-select-none !gl-shadow-none file-line-num"
:href="`#L${number}`"
:data-line-number="number"
>
{{ number }}
</a>
</div>
<pre
class="gl-p-0! gl-w-full gl-overflow-visible! gl-border-none! code highlight gl-leading-0"
><code><span :id="`LC${number}`" v-safe-html="content" :lang="language" class="line" data-testid="content"></span></code></pre>
</div>
</template>

120
app/assets/javascripts/vue_shared/components/source_viewer/components/chunk_new.vue
View File

@ -1,120 +0,0 @@
<script>
import { GlIntersectionObserver } from '@gitlab/ui';
import SafeHtml from '~/vue_shared/directives/safe_html';
import { getPageParamValue, getPageSearchString } from '~/blob/utils';
/*
* We only highlight the chunk that is currently visible to the user.
* By making use of the Intersection Observer API we can determine when a chunk becomes visible and highlight it accordingly.
*
* Content that is not visible to the user (i.e. not highlighted) does not need to look nice,
* so by rendering raw (non-highlighted) text, the browser spends less resources on painting
* content that is not immediately relevant.
* Why use plaintext as opposed to hiding content entirely?
* If content is hidden entirely, native find text (⌘ + F) won't work.
*/
export default {
components: {
GlIntersectionObserver,
},
directives: {
SafeHtml,
},
props: {
isHighlighted: {
type: Boolean,
required: true,
},
chunkIndex: {
type: Number,
required: false,
default: 0,
},
rawContent: {
type: String,
required: true,
},
highlightedContent: {
type: String,
required: true,
},
totalLines: {
type: Number,
required: false,
default: 0,
},
startingFrom: {
type: Number,
required: false,
default: 0,
},
blamePath: {
type: String,
required: true,
},
},
data() {
return {
hasAppeared: false,
};
},
computed: {
shouldHighlight() {
return Boolean(this.highlightedContent) && (this.hasAppeared || this.isHighlighted);
},
pageSearchString() {
const page = getPageParamValue(this.number);
return getPageSearchString(this.blamePath, page);
},
codeStyling() {
const defaultGutterWidth = 96;
return { marginLeft: `${this.$refs.lineNumbers?.offsetWidth || defaultGutterWidth}px` };
},
},
methods: {
handleChunkAppear() {
this.hasAppeared = true;
this.$emit('appear');
},
calculateLineNumber(index) {
return this.startingFrom + index + 1;
},
},
};
</script>
<template>
<div class="gl-display-flex">
<div v-if="shouldHighlight" class="gl-display-flex gl-flex-direction-column gl-absolute">
<div
v-for="(n, index) in totalLines"
:key="index"
data-testid="line-numbers"
class="gl-p-0! gl-z-3 diff-line-num gl-border-r gl-display-flex line-links line-numbers"
>
<a
class="gl-select-none !gl-shadow-none file-line-blame"
data-event-tracking="click_chunk_blame_on_blob_page"
:href="`${blamePath}${pageSearchString}#L${calculateLineNumber(index)}`"
></a>
<a
:id="`L${calculateLineNumber(index)}`"
class="gl-select-none !gl-shadow-none file-line-num"
:href="`#L${calculateLineNumber(index)}`"
:data-line-number="calculateLineNumber(index)"
>
{{ calculateLineNumber(index) }}
</a>
</div>
</div>
<div v-else ref="lineNumbers" class="line-numbers gl-p-0! gl-mr-3 gl-text-transparent">
<!-- Placeholder for line numbers while content is not highlighted -->
</div>
<gl-intersection-observer class="gl-w-full" @appear="handleChunkAppear">
<pre
class="gl-m-0 gl-p-0! gl-w-full gl-overflow-visible! gl-border-none! code highlight gl-leading-0"
><code v-if="shouldHighlight" v-safe-html="highlightedContent" :style="codeStyling" data-testid="content"></code><code v-else v-once class="line !gl-whitespace-pre-wrap gl-ml-1" data-testid="content" v-text="rawContent"></code></pre>
</gl-intersection-observer>
</div>
</template>

8
app/assets/javascripts/vue_shared/components/source_viewer/source_viewer.vue
View File

@ -6,7 +6,7 @@ import Tracking from '~/tracking';
import addBlobLinksTracking from '~/blob/blob_links_tracking';
import LineHighlighter from '~/blob/line_highlighter';
import { EVENT_ACTION, EVENT_LABEL_VIEWER, CODEOWNERS_FILE_NAME } from './constants';
import Chunk from './components/chunk_new.vue';
import Chunk from './components/chunk.vue';
import Blame from './components/blame_info.vue';
import { calculateBlameOffset, shouldRender, toggleBlameClasses } from './utils';
import blameDataQuery from './queries/blame_data.query.graphql';
@ -141,11 +141,11 @@ export default {
</script>
<template>
<div class="gl-display-flex">
<div class="gl-flex">
<blame v-if="showBlame && blameInfo.length" :blame-info="blameInfo" />
<div
class="file-content code js-syntax-highlight blob-content gl-display-flex gl-flex-direction-column gl-overflow-auto gl-w-full blob-viewer"
class="file-content code js-syntax-highlight blob-content blob-viewer gl-flex gl-w-full gl-flex-col gl-overflow-auto"
:class="$options.userColorScheme"
data-type="simple"
:data-path="blob.path"
@ -153,7 +153,7 @@ export default {
>
<codeowners-validation
v-if="isCodeownersFile"
class="gl-text-black-normal"
class="gl-text-gray-900"
:current-ref="currentRef"
:project-path="projectPath"
:file-path="blob.path"

6
app/assets/javascripts/vue_shared/components/source_viewer/utils.js
View File

@ -1,7 +1,7 @@
const BLAME_INFO_CLASSLIST = ['gl-border-t', 'gl-border-gray-500'];
const PADDING_TOP_SMALL = 'gl-pt-3!';
const PADDING_BOTTOM_LARGE = 'gl-pb-6!';
const PADDING_BOTTOM_SMALL = 'gl-pb-3!';
const PADDING_TOP_SMALL = '!gl-pt-3';
const PADDING_BOTTOM_LARGE = '!gl-pb-6';
const PADDING_BOTTOM_SMALL = '!gl-pb-3';
const VIEWER_SELECTOR = '.file-holder .blob-viewer';
const findLineNumberElement = (lineNumber) => document.getElementById(`L${lineNumber}`);

22
app/assets/javascripts/vue_shared/components/usage_quotas/usage_banner.vue
View File

@ -18,21 +18,17 @@ export default {
};
</script>
<template>
<div class="gl-display-flex gl-flex-direction-column">
<div class="gl-display-flex gl-align-items-center gl-py-3">
<div
class="gl-display-flex gl-flex-direction-column gl-sm-flex-direction-row gl-justify-content-space-between gl-align-items-stretch gl-flex-grow-1"
>
<div
class="gl-display-flex gl-flex-direction-column gl-mb-3 gl-sm-mb-0 gl-min-w-0 gl-flex-grow-1"
>
<div class="gl-flex gl-flex-col">
<div class="gl-flex gl-items-center gl-py-3">
<div class="gl-flex gl-grow gl-flex-col gl-items-stretch gl-justify-between sm:gl-flex-row">
<div class="gl-mb-3 gl-flex gl-min-w-0 gl-grow gl-flex-col sm:gl-mb-0">
<div
v-if="
/* eslint-disable-line @gitlab/vue-prefer-dollar-scopedslots */ $slots[
'left-primary-text'
]
"
class="gl-display-flex gl-align-items-center gl-text-body gl-font-bold gl-min-h-6 gl-min-w-0"
class="gl-flex gl-min-h-6 gl-min-w-0 gl-items-center gl-font-bold gl-text-primary"
>
<slot name="left-primary-text"></slot>
</div>
@ -42,13 +38,13 @@ export default {
'left-secondary-text'
]
"
class="gl-display-flex gl-align-items-center gl-text-gray-500 gl-min-h-6 gl-min-w-0 gl-flex-grow-1 gl-w-7/10 gl-md-max-w-70p"
class="gl-flex gl-min-h-6 gl-w-7/10 gl-min-w-0 gl-grow gl-items-center gl-text-gray-500 md:gl-max-w-7/10"
>
<slot name="left-secondary-text"></slot>
</div>
</div>
<div
class="gl-display-flex gl-flex-direction-column gl-sm-align-items-flex-end gl-justify-content-space-between gl-text-gray-500 gl-flex-shrink-0"
class="gl-flex gl-flex-shrink-0 gl-flex-col gl-justify-between gl-text-gray-500 sm:gl-items-end"
>
<div
v-if="
@ -56,7 +52,7 @@ export default {
'right-primary-text'
]
"
class="gl-display-flex gl-align-items-center gl-sm-text-body sm:gl-font-bold gl-min-h-6"
class="gl-flex gl-min-h-6 gl-items-center sm:gl-font-bold sm:gl-text-primary"
>
<slot name="right-primary-text"></slot>
</div>
@ -66,7 +62,7 @@ export default {
'right-secondary-text'
]
"
class="gl-display-flex gl-align-items-center gl-min-h-6"
class="gl-flex gl-min-h-6 gl-items-center"
>
<slot v-if="!loading" name="right-secondary-text"></slot>
<gl-skeleton-loader v-else :width="60" :lines="1" />

3
app/graphql/resolvers/ci/all_jobs_resolver.rb
View File

@ -44,7 +44,8 @@ module Resolvers
web_path: [{ project: { namespace: [:route] } }],
tags: [:tags],
ai_failure_analysis: [{ project: [:project_feature, :namespace] }],
trace: [{ project: [:namespace] }, :job_artifacts_trace]
trace: [{ project: [:namespace] }, :job_artifacts_trace],
source: [:build_source]
}
end

7
app/graphql/types/ci/job_type.rb
View File

@ -129,6 +129,9 @@ module Types
field :failure_message, GraphQL::Types::String, null: true,
description: 'Message on why the job failed.'
field :source, GraphQL::Types::String, null: true,
description: 'Policy or action that initiated the job. If not set, the value is inherited from the pipeline.'
def can_play_job?
object.playable? && Ability.allowed?(current_user, :play_job, object)
end
@ -163,6 +166,10 @@ module Types
object.job_artifacts if object.is_a?(::Ci::Build)
end
def source
object.source if object.is_a?(::Ci::Build)
end
def trace
object.trace if object.has_trace?
end

7
app/models/merge_request.rb
View File

@ -1,6 +1,8 @@
# frozen_string_literal: true
class MergeRequest < ApplicationRecord
extend Gitlab::Cache::RequestCache
include AtomicInternalId
include IidRoutes
include Issuable
@ -906,6 +908,11 @@ class MergeRequest < ApplicationRecord
end
end
def changed_paths
project.repository.find_changed_paths(commits, merge_commit_diff_mode: :all_parents)
end
request_cache(:changed_paths) { [id, diff_head_sha] }
def new_paths
diffs.diff_files.map(&:new_path)
end

2
config/events/schema.json
View File

@ -86,7 +86,7 @@
"additionalProperties": false
}
},
"additionalProperties": false
"additionalProperties": true
},
"iglu_schema_url": {
"type": [

9
config/feature_flags/beta/use_sidekiq_dedup_signaling.yml
View File

@ -1,9 +0,0 @@
---
name: use_sidekiq_dedup_signaling
feature_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/471239
introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/159215
rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/472741
milestone: '17.3'
group: group::scalability
type: beta
default_enabled: false

48
doc/administration/admin_area.md
View File

@ -13,12 +13,12 @@ DETAILS:
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.7 and later: on the left sidebar, at the bottom, 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.7 and later: on the left sidebar, at the bottom, select **Admin**.
- In GitLab 16.1 and later: on the left sidebar, select **Search or go to**, then select **Admin**.
- In GitLab 16.0 and earlier: on the top bar, select **Main menu > Admin**.
If the GitLab instance uses Admin Mode, you must [enable Admin Mode for your session](settings/sign_in_restrictions.md#turn-on-admin-mode-for-your-session) before
the **Admin area** button is visible.
the **Admin** button is visible.
NOTE:
Only administrators on GitLab self-managed or GitLab Dedicated can access the Admin area. On GitLab.com the Admin area feature is not available.
@ -36,7 +36,7 @@ You can administer all organizations in the GitLab instance from the Admin area'
To access the Organizations page:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Organizations**.
## Administering projects
@ -45,7 +45,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Projects**.
1. Select the **All**, **Private**, **Internal**, or **Public** tab to list only
projects of that criteria.
@ -98,7 +98,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
You can use the user search box to search and filter users by:
@ -137,7 +137,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Overview > Users**.
1. From the list of users, select a user.
1. Select **Impersonate**.
@ -146,7 +146,7 @@ You can impersonate a user in the following ways:
All impersonation activities are [captured with audit events](audit_event_reports.md#user-impersonation).
By default, impersonation is enabled. GitLab can be configured to [disable impersonation](../api/rest/index.md#disable-impersonation).
![user impersonation button](img/impersonate_user_button_v13_8.png)
![The user impersonation button.](img/impersonate_user_button_v13_8.png)
### User identities
@ -154,7 +154,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. From the list of users, select a user.
1. Select **Identities**.
@ -182,7 +182,7 @@ The following data is included in the export:
Only the first 100,000 user accounts are exported.
![user permission export button](img/export_permissions_v13_11.png)
![The user permission export button.](img/export_permissions_v13_11.png)
### Users statistics
@ -201,7 +201,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Locate the user and select them.
1. Select **Edit**.
@ -217,7 +217,7 @@ The [Cohorts](user_cohorts.md) tab displays the monthly cohorts of new users and
By default, users can create top level groups. To prevent a user from creating a top level group:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Locate the user and select them.
1. Select **Edit**.
@ -232,7 +232,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Groups**.
For each group, the page displays their name, description, size, number of projects in the group,
@ -256,14 +256,14 @@ You can categorize and find similar projects with [topics](../user/project/proje
To view all topics in the GitLab instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
For each topic, the page displays its name and the number of projects labeled with the topic.
### Search for topics
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
1. In the search box, enter your search criteria.
The topic search is case-insensitive and applies partial matching.
@ -272,7 +272,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
1. Select **New topic**.
1. Enter the **Topic slug (name)** and **Topic title**.
@ -291,7 +291,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
1. Select **Edit** in that topic's row.
1. Edit the topic slug (name), title, description, or avatar.
@ -302,7 +302,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
1. To remove a topic, select **Remove** in that topic's row.
@ -314,7 +314,7 @@ After a merged topic is deleted, you cannot restore it.
To merge topics:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Topics**.
1. Select **Merge topics**.
1. From the **Source topic** dropdown list, select the topic you want to merge and remove.
@ -328,7 +328,7 @@ page. For more details, see [Gitaly](gitaly/index.md).
To access the **Gitaly servers** page:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Gitaly servers**.
For each Gitaly server, the following details are listed:
@ -352,7 +352,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **CI/CD > Runners**.
#### Search and filter runners
@ -369,7 +369,7 @@ You can also filter runners by status, type, and tag. To filter:
1. Select any **Type**, or filter by **Status** or **Tags**.
1. Select or enter your search criteria.
![Attributes of a runner filtered by status](img/index_runners_search_or_filter_v14_5.png)
![Attributes of a runner filtered by status.](img/index_runners_search_or_filter_v14_5.png)
#### Bulk delete runners
@ -378,7 +378,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Runners**.
1. To the left of the runners you want to delete, select the checkbox.
To select all of the runners on the page, select the checkbox above
@ -408,7 +408,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
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**
tab to list only jobs of that status.

2
doc/administration/analytics.md
View File

@ -21,6 +21,6 @@ Prerequisites:
To enable ClickHouse:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. In the **Analytics** section, select the **Enable ClickHouse** checkbox.

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

@ -60,7 +60,7 @@ You can use DevOps Adoption to:
To view DevOps Reports:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Analytics > DevOps Reports**.
The **Overview tab** displays the number of features adopted in each category by the groups that use DevOps Reports.
@ -71,6 +71,6 @@ The **Adoption by group** table lists the features used by each group.
To add a group to or remove a group from DevOps Reports:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Analytics > DevOps Reports**.
1. From the **Add or remove groups** dropdown list, select the group you want to add or remove.

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

@ -20,7 +20,7 @@ Prerequisites:
To view instance-level analytics:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Analytics**, then one of the available analytics:
- [DevOps Reports](dev_ops_reports.md): Provides an overview of your entire instance's feature usage.

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

@ -17,7 +17,7 @@ Usage trends data refreshes daily.
To view usage trends:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Analytics > Usage trends**.
## Total counts

22
doc/administration/appearance.md
View File

@ -14,7 +14,7 @@ You can update your settings to change the look and feel of your GitLab self-man
To open the **Appearance** settings:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
## Customize your homepage button
@ -29,7 +29,7 @@ Replace the default **GitLab logo** **{tanuki}** with any image.
To customize your **Homepage** icon image:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Under **Navigation bar**, select **Choose file**.
1. At the bottom of the page, select **Update appearance settings**.
@ -42,7 +42,7 @@ Customize the appearance of the favicon. A favicon is the icon for a website tha
To change the favicon:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Under **Favicon**, select **Choose file**.
1. At the bottom of the page, select **Update appearance settings**.
@ -58,7 +58,7 @@ Add a small header message, a small footer message, or both, to the interface of
To add a system header, footer message, or both:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **System header and footer** section.
1. Complete the fields.
@ -75,7 +75,7 @@ Customize the title, description, and logo on the sign-in and register page. By
To customize your sign-in and register page titles or descriptions:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Sign in/Sign up pages** section.
1. Complete the fields. You can format the page **Title** and **Description** with Markdown.
@ -86,7 +86,7 @@ To customize the logo on your sign-in and register pages:
- The file should be less than 1 MB.
- The image should be 128 pixels high. Images more than 128 px high will be resized.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Sign in/Sign up pages** section.
1. Under **Logo**, select **Choose file**.
@ -112,7 +112,7 @@ Customize the icon, display name, short name, and description for your Progressi
To add a Progressive Web App name and short name:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Progressive Web App (PWA)** section.
1. Complete the fields.
@ -122,7 +122,7 @@ To add a Progressive Web App name and short name:
To add a Progressive Web App description:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Progressive Web App (PWA)** section.
1. Complete the fields. You can format the **Description** with Markdown.
@ -130,7 +130,7 @@ To add a Progressive Web App description:
To customize your Progressive Web App icon:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Progressive Web App (PWA)** section.
1. Under **Icon**, select **Choose file**.
@ -157,7 +157,7 @@ Add a guideline message to the **New project page**. You can format your message
To add a guideline message to the **New project page**:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **New project pages** section.
1. Complete the fields. You can format your guidelines with Markdown.
@ -166,7 +166,7 @@ To add a guideline message to the **New project page**:
Add guidelines for profile images.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Appearance**.
1. Go to the **Profile image guideline** section.
1. Complete the fields. You can format your text with Markdown.

6
doc/administration/audit_event_reports.md
View File

@ -18,7 +18,7 @@ DETAILS:
You can view audit events from user actions across an entire GitLab instance.
To view instance audit events:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. Filter by the following:
- Member of the project (user) who performed the action
@ -39,7 +39,7 @@ DETAILS:
You can export the current view (including filters) of your instance audit events as a
CSV(comma-separated values) file. To export the instance audit events to CSV:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. Select the available search filters.
1. Select **Export as CSV**.
@ -86,7 +86,7 @@ When a user is [impersonated](../administration/admin_area.md#user-impersonation
- Audit events include information about the impersonating administrator.
- Extra audit events are recorded for the start and end of the administrator's impersonation session.
![Audit event with impersonated user](img/impersonated_audit_events_v15_7.png)
![An audit event with an impersonated user.](img/impersonated_audit_events_v15_7.png)
## Time zones

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

@ -56,7 +56,7 @@ Prerequisites:
To add a streaming destination for an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select **Add streaming destination** and select **HTTP endpoint** to show the section for adding destinations.
@ -75,7 +75,7 @@ Prerequisites:
To list the streaming destinations for an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand it and see all the custom HTTP headers.
@ -88,7 +88,7 @@ Prerequisites:
To update a instance streaming destination's name:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -97,7 +97,7 @@ To update a instance streaming destination's name:
To update a instance streaming destination's custom HTTP headers:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -119,7 +119,7 @@ Prerequisites:
To delete the streaming destinations for an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -128,7 +128,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. To the right of the item, select **Edit** (**{pencil}**).
@ -155,7 +155,7 @@ Prerequisites:
To list streaming destinations for an instance and see the verification tokens:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. View the verification token on the right side of each item.
@ -171,7 +171,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 bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the stream to expand.
@ -213,7 +213,7 @@ Prerequisites:
To add Google Cloud Logging streaming destinations to an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select **Add streaming destination** and select **Google Cloud Logging** to show the section for adding destinations.
@ -230,7 +230,7 @@ Prerequisites:
To list Google Cloud Logging streaming destinations for an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the Google Cloud Logging stream to expand and see all the fields.
@ -243,7 +243,7 @@ Prerequisites:
To update Google Cloud Logging streaming destinations to an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the Google Cloud Logging stream to expand.
@ -261,7 +261,7 @@ Prerequisites:
To delete Google Cloud Logging streaming destinations to an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the Google Cloud Logging stream to expand.
@ -291,7 +291,7 @@ Prerequisites:
To add AWS S3 streaming destinations to an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select **Add streaming destination** and select **AWS S3** to show the section for adding destinations.
@ -307,7 +307,7 @@ Prerequisites:
To list AWS S3 streaming destinations for an instance.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the AWS S3 stream to expand and see all the fields.
@ -320,7 +320,7 @@ Prerequisites:
To update AWS S3 streaming destinations to an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the AWS S3 stream to expand.
@ -337,7 +337,7 @@ Prerequisites:
To delete AWS S3 streaming destinations on an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Audit events**.
1. On the main area, select the **Streams** tab.
1. Select the AWS S3 stream to expand.

2
doc/administration/auditor_users.md
View File

@ -38,7 +38,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Create a new user or edit an existing one. Set **Access Level** to **Auditor**.
1. If you created a user, select **Create user**. For an existing user, select **Save changes**.

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

@ -182,7 +182,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. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Select the name of the affected user.
1. In the upper-right corner, select **Edit**.
@ -239,7 +239,7 @@ field contains no data:
To resolve this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand both of the following:
- **Account and limit**.
@ -394,7 +394,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Overview > Users**.
1. Search for the user.
1. Open the user by selecting their name. Do not select **Edit**.

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

@ -414,7 +414,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Visibility and access controls**.
1. Ensure the **Lock memberships to LDAP synchronization** checkbox is selected.
@ -426,7 +426,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Visibility and access controls**.
1. Ensure the **Allow group owners to manage LDAP-related settings** checkbox is not checked.

2
doc/administration/auth/test_oidc_oauth.md
View File

@ -28,7 +28,7 @@ Before you can test OIDC/OAuth on GitLab, you must:
First, you must create OIDC/OAuth application on your GitLab instance. To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Applications**.
1. Select **Add new application**.
1. Fill in the details for your client application, including the name, redirect URI, and allowed scopes.

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

@ -88,7 +88,7 @@ To prepare the new server:
```
1. Disable periodic background jobs:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. Under the Sidekiq dashboard, select **Cron** tab and then
**Disable All**.
@ -199,7 +199,7 @@ to the new environment.
1. [Restore the GitLab backup](restore_gitlab.md).
1. Verify that the Redis database restored correctly:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. Under the Sidekiq dashboard, verify that the numbers
match with what was shown on the old server.

10
doc/administration/broadcast_messages.md
View File

@ -24,7 +24,7 @@ Broadcast messages can be managed using the [broadcast messages API](../api/broa
Banners are shown on the top of a page and optionally in the command line as a Git remote response.
![Broadcast Message Banner](img/broadcast_messages_banner_v15_0.png)
![A broadcast message banner displaying a welcome message.](img/broadcast_messages_banner_v15_0.png)
```shell
$ git push
@ -50,7 +50,7 @@ The available placeholders are:
If the user is not signed in, user related values are empty.
![Broadcast Message Notification](img/broadcast_messages_notification_v12_10.png)
![A broadcast message notification using the name placeholder.](img/broadcast_messages_notification_v12_10.png)
If more than one notification is active at one time, only the newest is shown.
@ -60,7 +60,7 @@ To display messages to users on your GitLab instance, add a broadcast message.
To add a broadcast message:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Messages**.
1. Select **Add new message**.
1. Add the text for the message to the **Message** field. You can style a message's content using Markdown, emoji, and the `a` and `br` HTML tags.
@ -88,7 +88,7 @@ If you must make changes to a broadcast message, you can edit it.
To edit a broadcast message:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Messages**.
1. From the list of broadcast messages, select the edit button for the message.
1. After making the required changes, select **Update broadcast message**.
@ -102,7 +102,7 @@ You can delete a broadcast message while it's active.
To delete a broadcast message:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Messages**.
1. From the list of broadcast messages, select the delete button for the message.

14
doc/administration/credentials_inventory.md
View File

@ -35,7 +35,7 @@ You can also [revoke](#revoke-a-users-personal-access-token), [delete](#delete-a
You can revoke a user's personal access token.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Credentials**.
1. By the personal access token, select **Revoke**.
@ -49,29 +49,29 @@ If a **Revoke** button is not available, the token may be expired or revoked, or
When a PAT is revoked from the credentials inventory, the instance notifies the user by email.
![Credentials inventory page - Personal access tokens](img/credentials_inventory_personal_access_tokens_v14_9.png)
![The credentials inventory page listing personal access tokens.](img/credentials_inventory_personal_access_tokens_v14_9.png)
## Revoke a user's project access token
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Credentials**.
1. Select the **Project Access Tokens** tab.
1. By the project access token, select **Revoke**.
The project access token is revoked and a background worker is queued to delete the project bot user.
![Credentials inventory page - Project access tokens](img/credentials_inventory_project_access_tokens_v14_9.png)
![The credentials inventory page listing project access tokens.](img/credentials_inventory_project_access_tokens_v14_9.png)
## Delete a user's SSH key
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Credentials**.
1. Select the **SSH Keys** tab.
1. By the SSH key, select **Delete**.
The instance notifies the user.
![Credentials inventory page - SSH keys](img/credentials_inventory_ssh_keys_v14_9.png)
![The credentials inventory page listing SSH keys.](img/credentials_inventory_ssh_keys_v14_9.png)
## Review existing GPG keys
@ -82,4 +82,4 @@ credentials inventory GPG Keys tab, as well as the following properties:
- The ID of the GPG key.
- Whether the GPG key is [verified or unverified](../user/project/repository/signed_commits/gpg.md).
![Credentials inventory page - GPG keys](img/credentials_inventory_gpg_keys_v14_9.png)
![The credentials inventory page listing GPG keys.](img/credentials_inventory_gpg_keys_v14_9.png)

2
doc/administration/custom_project_templates.md
View File

@ -29,7 +29,7 @@ might modify the template projects without understanding the side effects.
To select the group to manage the project templates for your instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Templates**.
1. Expand **Custom project templates**.
1. Select a group to use.

2
doc/administration/diff_limits.md
View File

@ -37,7 +37,7 @@ set values are presented as **Too large** are cannot be expanded in the UI.
To configure these values:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Diff limits**.
1. Enter a value for the diff limit.

2
doc/administration/email_from_gitlab.md
View File

@ -28,7 +28,7 @@ You can send email notifications once every 10 minutes.
To send an email:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the upper-right corner, select **Send email to users** (**{mail}**).
1. Complete the fields. The email body supports only plain text and does not support HTML, Markdown, or other rich text formats.

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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
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.
@ -55,7 +55,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.

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

@ -31,7 +31,7 @@ the site more time before scheduling a planned failover.
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Expand **Verification information** tab for that site to view automatic checksumming
status for repositories and wikis. Successes are shown in green, pending work
@ -41,7 +41,7 @@ On the **primary** site:
On the **secondary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Expand **Verification information** tab for that site to view automatic checksumming
status for repositories and wikis. Successes are shown in green, pending work
@ -69,7 +69,7 @@ increase load and vice versa.
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Select **Edit** for the **primary** site to customize the minimum
re-verification interval:
@ -102,7 +102,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Overview > Projects**.
1. Find the project that you want to check the checksum differences and
select its name.

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

@ -90,7 +90,7 @@ Note the following when promoting a secondary:
- If you are using a [location aware public URL](../secondary_proxy/location_aware_external_url.md), the runners should automatically connect to the new primary after the old primary is removed from the DNS entry.
- If you don't expect the runners connected to the previous primary to come back, you should remove them:
- Through the UI:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **CI/CD > Runners** and remove them.
- Using the [Runners API](../../../api/runners.md).

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

@ -151,7 +151,7 @@ ensure these processes are close to 100% as possible during active use.
On the **secondary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
Replicated objects (shown in green) should be close to 100%,
and there should be no failures (shown in red). If a large proportion of
@ -179,7 +179,7 @@ This [content was moved to another location](background_verification.md).
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Messages**.
1. Add a message notifying users on the maintenance window.
You can check under **Geo > Sites** to estimate how long it
@ -204,7 +204,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Cron**.
1. Select `Disable All` to disable non-Geo periodic background jobs.
@ -223,7 +223,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
those with `geo` in the name to drop to 0.
@ -238,7 +238,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`
queues to drop to 0 queued and 0 running jobs.

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

@ -69,7 +69,7 @@ promote a Geo replica and perform a failover.
On the **secondary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites** to see its status.
Replicated objects (shown in green) should be close to 100%,
and there should be no failures (shown in red). If a large proportion of
@ -108,7 +108,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
those with `geo` in the name to drop to 0.
@ -123,7 +123,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`
queues to drop to 0 queued and 0 running jobs.

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

@ -119,7 +119,7 @@ follow these steps to avoid unnecessary data loss:
connection.
1. On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**..
1. On the left sidebar, at the bottom, select **Admin**..
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Cron**.
1. Select `Disable All` to disable any non-Geo periodic background jobs.
@ -137,7 +137,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all queues except
those with `geo` in the name to drop to 0.
@ -152,7 +152,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Monitoring > Background jobs**.
1. On the Sidekiq dashboard, select **Queues**, and wait for all the `geo`
queues to drop to 0 queued and 0 running jobs.

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

@ -171,7 +171,7 @@ public URL of the primary site is used.
To update the internal URL of the primary Geo site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Select **Edit** on the primary site.
1. Change the **Internal URL**, then select **Save changes**.

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

@ -222,7 +222,7 @@ In the following steps, replace `<ssh_host_key_path>` with the one you're using:
```
1. Go to the primary node GitLab instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **Add site**.
![Add secondary site](img/adding_a_secondary_v15_8.png)
@ -331,7 +331,7 @@ method to be enabled. This is enabled by default, but if converting an existing
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Visibility and access controls**.
1. If using Git over SSH, then:
@ -346,7 +346,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Verify that it's correctly identified as a **secondary** Geo site, and that
Geo is enabled.

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

@ -169,7 +169,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Nodes**.
The initial replication, or "backfill", is probably still in progress.
@ -219,7 +219,7 @@ On multinode deployments, make sure that the issuer configured on the Sidekiq no
To help with troubleshooting, you can manually trigger the container registry replication process:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. In **Replication Details** for a **Secondary Site**, select **Container Repositories**.
1. Select **Resync** for one row, or **Resync all**.

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

@ -39,7 +39,7 @@ to do that.
To remove the **primary** site:
1. [Remove all secondary Geo sites](remove_geo_site.md)
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Nodes**.
1. Select **Remove** for the **primary** node.
1. Confirm by selecting **Remove** when the prompt appears.

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

@ -46,7 +46,7 @@ whether they are stored on the local file system or in object storage.
To enable GitLab replication:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Nodes**.
1. Select **Edit** on the **secondary** site.
1. In the **Synchronization Settings** section, find the **Allow this secondary node to replicate content on Object Storage**

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

@ -12,7 +12,7 @@ DETAILS:
**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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Nodes**.
1. For the **secondary** site you want to remove, select **Remove**.
1. Confirm by selecting **Remove** when the prompt appears.

4
doc/administration/geo/replication/troubleshooting/common.md
View File

@ -21,7 +21,7 @@ Before attempting more advanced troubleshooting:
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
We perform the following health checks on each **secondary** site
@ -584,7 +584,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Change the URL and save the change.

2
doc/administration/geo/replication/troubleshooting/failover.md
View File

@ -84,7 +84,7 @@ site's URL matches its external URL.
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Find the affected **secondary** site and select **Edit**.
1. Ensure the **URL** field matches the value found in `/etc/gitlab/gitlab.rb`

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

@ -17,7 +17,7 @@ in the background.
On the **primary** site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Select **Edit** of the secondary site you want to tune.
1. Under **Tuning settings**, there are several variables that can be tuned to

2
doc/administration/geo/secondary_proxy/runners.md
View File

@ -58,7 +58,7 @@ If you are not concerned about these issues, there is nothing to do here.
You must have administrator access to use any of the following methods:
- Through the Admin area:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Runners**.
1. Identify the runners you would like to pause.
1. Select the `pause` button next to each runner you would like to pause.

6
doc/administration/geo/setup/two_single_node_external_services.md
View File

@ -313,7 +313,7 @@ secondary site is a read-only copy.
```
1. Go to the primary node GitLab instance:
1. On the left sidebar, at the bottom, select **Admin area**..
1. On the left sidebar, at the bottom, select **Admin**..
1. Select **Geo > Sites**.
1. Select **Add site**.
@ -368,7 +368,7 @@ If you convert an existing site to Geo, you should check that the clone method i
On the primary site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Visibility and access controls**.
1. If you use Git over SSH:
@ -383,7 +383,7 @@ the primary site.
After you sign in:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Verify that the site is correctly identified as a secondary Geo site, and that
Geo is enabled.

6
doc/administration/geo/setup/two_single_node_sites.md
View File

@ -567,7 +567,7 @@ You must manually replicate the secret file across all of your secondary sites,
```
1. Go to the primary node GitLab instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Select **Add site**.
@ -622,7 +622,7 @@ If you convert an existing site to Geo, you should check that the clone method i
On the primary site:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Visibility and access controls**.
1. If you use Git over SSH:
@ -637,7 +637,7 @@ the primary site.
After you sign in:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Verify that the site is correctly identified as a secondary Geo site, and that
Geo is enabled.

4
doc/administration/geo_sites.md
View File

@ -15,7 +15,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
## Common settings
@ -73,7 +73,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Geo > Sites**.
1. Select **Edit** on the site you want to customize.
1. Edit the internal URL.

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

@ -1352,7 +1352,7 @@ Particular attention should be shown to:
1. Check that the Praefect storage is configured to store new repositories:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Settings > Repository**.
1. Expand the **Repository storage** section.

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

@ -23,7 +23,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Gitaly servers**.
1. Confirm all Gitaly servers indicate that they are up to date.

2
doc/administration/guest_users.md
View File

@ -60,7 +60,7 @@ By default, new users are not assigned the Guest role.
To assign the Guest role to new users:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview** > **Users**.
1. Select the relevant user or [create a new one](../user/profile/account/create_accounts.md).
1. In the **Max Role** column, select **Guest**.

2
doc/administration/housekeeping.md
View File

@ -80,7 +80,7 @@ frequently.
You can change how often Gitaly is asked to optimize a repository.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Repository**.
1. Expand **Repository maintenance**.
1. In the **Housekeeping** section, configure the housekeeping options.

2
doc/administration/inactive_project_deletion.md
View File

@ -27,7 +27,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Repository**.
1. Expand **Repository maintenance**.
1. In the **Inactive project deletion** section, select **Delete inactive projects**.

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

@ -50,7 +50,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Diagrams.net**.
1. Select the **Enable Diagrams.net** checkbox.

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

@ -18,7 +18,7 @@ you can create diagrams-as-code within AsciiDoc, Markdown, reStructuredText, and
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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Go to **Settings > General**.
1. Expand the **Kroki** section.
1. Select **Enable Kroki** checkbox.

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

@ -46,7 +46,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, go to **Settings > General** and expand the **Mailgun** section.
1. Select the **Enable Mailgun** checkbox.
1. Enter the Mailgun HTTP webhook signing key as described in

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

@ -324,7 +324,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, go to **Settings > General** and expand the **PlantUML** section.
1. Select the **Enable PlantUML** checkbox.
1. Set the PlantUML instance as `https://gitlab.example.com/-/plantuml/`,

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

@ -115,6 +115,6 @@ 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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Web terminal**.
1. Set a `max session time`.

2
doc/administration/labels.md
View File

@ -12,7 +12,7 @@ DETAILS:
To manage labels for the GitLab instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Labels**.
For more details on how to manage labels, see [Labels](../user/project/labels.md).

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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Subscription**.
1. Paste the activation code in **Activation code**.
1. Read and accept the terms of service.

6
doc/administration/license_file.md
View File

@ -16,7 +16,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. In the **Add License** area, add a license by either uploading the file or entering the key.
1. Select the **Terms of Service** checkbox.
@ -100,7 +100,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Subscription**.
1. Select **Remove license**.
@ -110,7 +110,7 @@ Repeat these steps to remove all licenses, including those applied in the past.
To view your license details:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Subscription**.
You can add and view more than one license, but only the latest license in

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

@ -23,7 +23,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Maintenance Mode**, and toggle **Enable Maintenance Mode**.
You can optionally add a message for the banner as well.
@ -47,7 +47,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Settings > General**.
1. Expand **Maintenance Mode**, and toggle **Enable Maintenance Mode**.
You can optionally add a message for the banner as well.
@ -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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. 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

@ -21,7 +21,7 @@ and can no longer be changed:
To enable merge request approval settings for an instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Push rules**.
1. Expand **Merge request approvals**.
1. Choose the required options.

28
doc/administration/moderate_users.md
View File

@ -47,7 +47,7 @@ sign in.
To view user sign ups pending approval:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Pending approval**, and press <kbd>Enter</kbd>.
@ -59,7 +59,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Pending approval** and press <kbd>Enter</kbd>.
1. For the user sign up you want to approve or reject, select the vertical ellipsis (**{ellipsis_v}**), then **Approve** or **Reject**.
@ -96,7 +96,7 @@ You can block a user's access to the instance.
To block a user:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. For the user you want to block, select the vertical ellipsis (**{ellipsis_v}**), then **Block**.
@ -110,7 +110,7 @@ To report abuse from other users, see [report abuse](../user/report_abuse.md). F
A blocked user can be unblocked from the Admin area. To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Blocked** and press <kbd>Enter</kbd>.
1. For the user you want to unblock, select the vertical ellipsis (**{ellipsis_v}**), then **Unblock**.
@ -124,7 +124,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Blocked** and press <kbd>Enter</kbd>.
1. Select a user.
@ -154,7 +154,7 @@ Prerequisites:
To deactivate a user:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. For the user you want to deactivate, select the vertical ellipsis (**{ellipsis_v}**) and then **Deactivate**.
1. On the dialog, select **Deactivate**.
@ -176,7 +176,7 @@ Administrators can enable automatic deactivation of users who either:
To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Under **Dormant users**, check **Deactivate dormant users after a period of inactivity**.
@ -230,7 +230,7 @@ A deactivated user can be activated from the Admin area.
To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Deactivated** and press <kbd>Enter</kbd>.
1. For the user you want to activate, select the vertical ellipsis (**{ellipsis_v}**), then **Activate**.
@ -262,7 +262,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. For the user you want to ban, select the vertical ellipsis (**{ellipsis_v}**), then **Ban user**.
@ -272,7 +272,7 @@ Users can be banned using the Admin area. To do this:
A banned user can be unbanned using the Admin area. To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box , filter by **State=Banned** and press <kbd>Enter</kbd>.
1. For the user you want to unban, select the vertical ellipsis (**{ellipsis_v}**), then **Unban user**.
@ -284,7 +284,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. For the user you want to delete, select the vertical ellipsis (**{ellipsis_v}**), then **Delete user**.
1. Type the username.
@ -295,7 +295,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. For the user you want to delete, select the vertical ellipsis (**{ellipsis_v}**), then **Delete user and contributions**.
1. Type the username.
@ -321,7 +321,7 @@ Prerequisites:
:::TabTitle Trust a user
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Select a user.
1. From the **User administration** dropdown list, select **Trust user**.
@ -331,7 +331,7 @@ The user is trusted.
:::TabTitle Untrust a user
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. In the search box, filter by **State=Trusted** and press <kbd>Enter</kbd>.
1. Select a user.

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

@ -22,7 +22,7 @@ and Grafana allows you to query the data to display graphs.
After setting up Grafana, you can enable a link to access it from the
GitLab sidebar:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Metrics and profiling**.
1. Expand **Metrics - Grafana**.
1. Select the **Add a link to Grafana** checkbox.

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

@ -105,7 +105,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Metrics and profiling**.
1. Expand **Profiling - Performance bar**.
1. Select **Allow non-administrators access to the performance bar**.

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

@ -13,7 +13,7 @@ DETAILS:
To enable the GitLab Prometheus metrics:
1. Log in to GitLab as a user with administrator access.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Metrics and profiling**.
1. Find the **Metrics - Prometheus** section, and select **Enable GitLab Prometheus metrics endpoint**.
1. [Restart GitLab](../../restart_gitlab.md#reconfigure-a-linux-package-installation) for the changes to take effect.

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

@ -130,7 +130,7 @@ users as long as a large file exists.
To disable writes to the `authorized_keys` file:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Performance optimization**.
1. Clear the **Use authorized_keys file to authenticate SSH keys** checkbox.
@ -149,7 +149,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Settings > Network**.
1. Expand **Performance optimization**.
1. Select the **Use authorized_keys file to authenticate SSH keys** checkbox.

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

@ -355,7 +355,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Container Registry**.
1. For the **Authorization token duration (minutes)**, update the value.

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

@ -570,7 +570,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Pages**.
1. Clear the **Require users to prove ownership of custom domains** checkbox.
@ -585,7 +585,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Pages**.
1. Enter the email address for receiving notifications and accept Let's Encrypt's Terms of Service.
@ -636,7 +636,7 @@ pre-existing applications must modify the GitLab Pages OAuth application. Follow
this:
1. Enable [access control](#access-control).
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Applications**.
1. Expand **GitLab Pages**.
1. Clear the `api` scope's checkbox and select the desired scope's checkbox (for example,
@ -653,7 +653,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Pages**.
1. Select the **Disable public access to Pages sites** checkbox.
@ -895,7 +895,7 @@ Prerequisites:
To set the global maximum pages size for a project:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Pages**.
1. In **Maximum size of pages**, enter a value. The default is `100`.
@ -944,7 +944,7 @@ Prerequisites:
To set the maximum number of GitLab Pages custom domains for a project:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. 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

@ -482,7 +482,7 @@ The default for the maximum size of unpacked archives per project is 100 MB.
To change this value:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Pages**.
1. Update the value for **Maximum size of pages (MB)**.

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

@ -173,7 +173,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Applications > GitLab Pages**.
1. Edit the application.
1. Under **Scopes**, ensure that the `api` scope is selected.
@ -216,7 +216,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Applications** and then **Add new application**.
1. Ensure the **Callback URL/Redirect URI** is using the protocol (HTTP or HTTPS) that
`pages_external_url` is configured to use.

2
doc/administration/polling.md
View File

@ -30,7 +30,7 @@ The default value (`1`) is recommended for the majority of GitLab installations.
To adjust the polling interval multiplier:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Polling interval multiplier**.
1. Set a value for the polling interval multiplier. This multiplier is applied to all resources at

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

@ -25,7 +25,7 @@ GitLab team members can view more information in this confidential epic:
## Configure Git abuse rate limiting
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Reporting**.
1. Expand **Git abuse rate limit**.
1. Update the Git abuse rate limit settings:
@ -44,7 +44,7 @@ If automatic banning is enabled, an email notification is sent when a user is ab
## Unban a user
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.
1. Select the **Banned** tab and search for the account you want to unban.
1. From the **User administration** dropdown list select **Unban user**.

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

@ -23,7 +23,7 @@ unique IP addresses. Therefore, the IP addresses per user limit should take into
## Configure IP address restrictions
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Reporting**.
1. Expand **Spam and Anti-bot Protection**.
1. Update the IP address restrictions settings:

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

@ -42,7 +42,7 @@ Spamcheck is only available for package-based installations:
## Configure GitLab to use Spamcheck
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Reporting**.
1. Expand **Spam and Anti-bot Protection**.
1. Update the Spam Check settings:

6
doc/administration/repository_checks.md
View File

@ -28,7 +28,7 @@ repository consistency checks, some disabled checks, and how to configure consis
To check a project's repository using GitLab UI:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Projects**.
1. Select the project to check.
1. In the **Repository check** section, select **Trigger repository check**.
@ -40,7 +40,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Repository**.
1. Expand **Repository maintenance**.
1. Enable **Enable repository checks**.
@ -94,7 +94,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Repository**.
1. Expand **Repository maintenance**.
1. Select **Clear all repository checks**.

4
doc/administration/repository_storage_paths.md
View File

@ -70,7 +70,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Projects** and select the project.
1. Locate the **Relative path** field. The value is similar to:
@ -227,7 +227,7 @@ LFS objects are also [S3-compatible](lfs/index.md#storing-lfs-objects-in-remote-
After you [configure multiple repository storages](https://docs.gitlab.com/omnibus/settings/configuration.html#store-git-data-in-an-alternative-directory), you can choose where new repositories are stored:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Repository**.
1. Expand **Repository storage**.
1. Enter values in the **Storage nodes for new repositories** fields.

4
doc/administration/review_abuse_reports.md
View File

@ -19,7 +19,7 @@ reports in the Admin area.
To receive notifications of new abuse reports by email:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Reporting**.
1. Expand the **Abuse reports** section.
1. Provide an email address and select **Save changes**.
@ -38,7 +38,7 @@ To find out more about reporting abuse, see
To access abuse reports:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Abuse reports**.
There are four ways to resolve an abuse report, with a button for each method:

2
doc/administration/review_spam_logs.md
View File

@ -22,7 +22,7 @@ View and resolve spam logs to moderate user activity in your instance.
To view spam logs:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Spam logs**.
1. Optional. To resolve a spam log, select **More actions** (**{ellipsis_v}**), then **Remove user**, **Block user**, **Remove log**, or **Trust user**.

4
doc/administration/self_hosted_models/configure_duo_features.md
View File

@ -42,7 +42,7 @@ Prerequisites:
To configure a self-hosted model:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **AI-powered features**.
- If the **AI-powered features** menu item is not available, synchronize your
subscription after purchase:
@ -67,7 +67,7 @@ Prerequisites:
To configure the AI-powered features to use your model:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **AI-powered features**.
- If the **AI-powered features** menu item is not available, synchronize your
subscription after purchase:

2
doc/administration/server_hooks.md
View File

@ -80,7 +80,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
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
hooks must be located.

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

@ -20,7 +20,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Increase or decrease that **Default projects limit** value.
@ -33,7 +33,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview** > **Users**.
1. From the list of users, select a user.
1. Select **Edit**.
@ -46,7 +46,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Increase or decrease by changing the value in **Maximum attachment size (MiB)**.
@ -61,7 +61,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Increase or decrease by changing the value in **Maximum push size (MiB)**.
@ -90,7 +90,7 @@ The default prefix is `glpat-` but administrators can change it.
To change the default global prefix:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Fill in the **Personal Access Token prefix** field.
@ -140,7 +140,7 @@ These settings can be found in:
1. Fill in the **Repository size limit (MiB)** field in the **Naming, visibility** section.
1. Select **Save changes**.
- GitLab global settings:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Fill in the **Size limit per repository (MiB)** field.
@ -162,7 +162,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**. The set duration is in **Session duration (minutes)**.
@ -180,7 +180,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Select or clear the **Remember me** checkbox to turn this setting on or off.
@ -198,7 +198,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Fill in the **Session duration for Git operations when 2FA is enabled (minutes)** field.
@ -225,7 +225,7 @@ there are no restrictions.
To set a lifetime on how long SSH keys are valid:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Fill in the **Maximum allowable lifetime for SSH keys (days)** field.
@ -263,7 +263,7 @@ there are no restrictions.
To set a lifetime on how long access tokens are valid:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Account and limit** section.
1. Fill in the **Maximum allowable lifetime for access tokens (days)** field.
@ -287,7 +287,7 @@ To maintain integrity of user details in [audit events](../../administration/aud
To do this:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Select the **Prevent users from changing their profile name** checkbox.
@ -309,7 +309,7 @@ On self-managed GitLab, by default this feature is not available. To make it ava
By default, users can create organizations. GitLab administrators can prevent users from creating organizations.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Clear the **Allow users to create organizations** checkbox.
@ -325,7 +325,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Clear the **Allow new users to create top-level groups** checkbox.
@ -337,7 +337,7 @@ By default, new users can create top-level groups. GitLab administrators can pre
By default, users with the Guest role can create projects and groups.
GitLab administrators can prevent this behavior:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Clear the **Allow users with up to Guest role to create groups and personal projects** checkbox.
@ -360,7 +360,7 @@ This feature is available for testing, but not ready for production use.
By default, users can make their profiles private.
GitLab administrators can disable this setting to prevent users from making their profiles private:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Clear the **Allow users to make their profiles private** checkbox.
@ -380,7 +380,7 @@ For more information, see [issue 461701](https://gitlab.com/gitlab-org/gitlab/-/
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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Select the **Make new users' profiles private by default** checkbox.
@ -400,7 +400,7 @@ DETAILS:
By default, users can delete their own accounts. GitLab administrators can prevent
users from deleting their own accounts:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Account and limit**.
1. Clear the **Allows users to delete their own accounts** checkbox.

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

@ -18,7 +18,7 @@ job artifacts.
To enable (or disable) [Auto DevOps](../../topics/autodevops/index.md)
for all projects:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Check (or uncheck to disable) the box that says **Default to Auto DevOps pipeline for all projects**.
1. Optionally, set up the [Auto DevOps base domain](../../topics/autodevops/requirements.md#auto-devops-base-domain)
@ -35,7 +35,7 @@ If you want to disable it for a specific project, you can do so in
You can set all new projects to have instance runners available by default.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
1. Select the **Enable instance runners for new projects** checkbox.
@ -54,7 +54,7 @@ Users must use runner authentication tokens instead.
If you have not yet [migrated to the use of runner authentication tokens](../../ci/runners/new_creation_workflow.md),
you can enable runner registration tokens. This setting and support for runner registration tokens will be removed in GitLab 18.0.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
1. Select the **Allow runner registration token** checkbox.
@ -71,7 +71,7 @@ you can assign that runner to other projects.
To enable a project runner for more than one project:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. From the left sidebar, select **CI/CD > Runners**.
1. Select the runner you want to edit.
1. In the upper-right corner, select **Edit** (**{pencil}**).
@ -84,7 +84,7 @@ To enable a project runner for more than one project:
To display details about the instance runners in all projects'
runner settings:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
1. Enter text, including Markdown if you want, in the **Instance runner details** field.
@ -112,7 +112,7 @@ The value is in MB, and the default value is 100 MB per job. An administrator ca
- Instance:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. On the left sidebar, select **Settings > CI/CD > Continuous Integration and Deployment**.
1. Change the value of **Maximum artifacts size (MB)**.
1. Select **Save changes** for the changes to take effect.
@ -136,7 +136,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Change the value of default expiration time.
1. Select **Save changes** for the changes to take effect.
@ -165,7 +165,7 @@ If disabled for the entire instance, you cannot enable this in individual projec
To disable the setting:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
1. Clear the **Keep the latest artifacts for all jobs in the latest successful pipelines** checkbox.
@ -184,7 +184,7 @@ display a lock icon (**{lock}**) and **This job is archived** at the top of the
To set the duration for which the jobs are considered as old and expired:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Continuous Integration and Deployment** section.
1. Set the value of **Archive jobs**.
@ -201,7 +201,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Select **Protect CI/CD variables by default**.
@ -212,7 +212,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 for the entire instance.
The default is `150`.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Change the value of **Maximum includes**.
1. Select **Save changes** for the changes to take effect.
@ -225,7 +225,7 @@ The maximum number of [downstream pipelines](../../ci/pipelines/downstream_pipel
(for a given project, user, and commit) can be set for the entire instance.
The default value is `0` (no restriction).
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Change the value of **Maximum downstream pipeline trigger rate**.
1. Select **Save changes** for the changes to take effect.
@ -235,7 +235,7 @@ The default value is `0` (no restriction).
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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Input the new file and path in the **Default CI/CD configuration file** field.
1. Select **Save changes** for the changes to take effect.
@ -249,7 +249,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Continuous Integration and Deployment** section.
1. In the **CI/CD limits** section, you can set the following limits:
@ -271,7 +271,7 @@ walkthrough on how to add one.
To enable or disable the banner:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Select or clear the **Enable pipeline suggestion banner** checkbox.
1. Select **Save changes**.
@ -286,7 +286,7 @@ malicious user-generated content, as described in
Self-managed administrators can disable the external redirect warning page,
so you can view job artifact pages directly:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Continuous Integration and Deployment**.
1. Deselect **Enable the external redirect page for job artifacts**.
@ -316,7 +316,7 @@ GitLab administrators can disable the forwarding of Maven requests to [Maven Cen
To disable forwarding Maven requests:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
1. Clear the checkbox **Forward Maven package requests to the Maven Registry if the packages are not found in the GitLab Package Registry**.
@ -332,7 +332,7 @@ GitLab administrators can disable the forwarding of npm requests to [npmjs.com](
To disable it:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
1. Clear the checkbox **Forward npm package requests to the npm Registry if the packages are not found in the GitLab Package Registry**.
@ -348,7 +348,7 @@ GitLab administrators can disable the forwarding of PyPI requests to [pypi.org](
To disable it:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
1. Clear the checkbox **Forward PyPI package requests to the PyPI Registry if the packages are not found in the GitLab Package Registry**.
@ -360,7 +360,7 @@ GitLab administrators can adjust the maximum allowed file size for each package
To set the maximum file size:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand the **Package Registry** section.
1. Find the package type you would like to adjust.
@ -380,7 +380,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
1. In the **Runner registration** section, clear the **Members of the project can register runners** and
@ -402,7 +402,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Groups** and find your group.
1. Select **Edit**.
1. Clear the **New group runners can be registered** checkbox if you want to disable runner registration by all members in the group. If the setting is read-only, you must enable runner registration for the [instance](#restrict-runner-registration-by-all-users-in-an-instance).
@ -416,7 +416,7 @@ By default, GitLab instances periodically fetch official runner version data fro
To disable your instance fetching this data:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > CI/CD**.
1. Expand **Runners**.
1. In the **Runner version management** section, clear the **Fetch GitLab Runner release version data from GitLab.com** checkbox.

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

@ -36,7 +36,7 @@ Prerequisites:
To override the general user and IP rate limits for requests to deprecated API endpoints:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Deprecated API Rate Limits**.
1. Select the checkboxes for the types of rate limits you want to enable:

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

@ -28,7 +28,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Select the **Include author name in email notification email body** checkbox.
@ -44,7 +44,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Select **Enable multipart email**.
@ -61,7 +61,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Enter the desired hostname in the **Custom hostname (for private commit emails)** field.
@ -83,7 +83,7 @@ can be used for legal, auditing, or compliance reasons, for example.
To add additional text to emails:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Enter your text in the **Additional text** field.
@ -95,7 +95,7 @@ GitLab sends email notifications to users when their account has been deactivate
To disable these notifications:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Clear the **Enable user deactivation emails** checkbox.
@ -122,7 +122,7 @@ setting.
To add additional text to deactivation emails:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Email**.
1. Enter your text in the **Additional text for deactivation email** field.

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

@ -49,7 +49,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **External authorization**.
1. Complete the fields.
@ -69,7 +69,7 @@ Prerequisites:
To allow authorization with deploy tokens and keys:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **External authorization**, and:
- Leave the service URL field empty.

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

@ -31,7 +31,7 @@ Prerequisites:
To override the general user and IP rate limits for requests to the Repository files API:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Files API Rate Limits**.
1. Select the checkboxes for the types of rate limits you want to enable:

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

@ -24,7 +24,7 @@ Permissions-Policy: interest-cohort=()
To enable it:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Federated Learning of Cohorts (FLoC)**.
1. Select the **Participate in FLoC** checkbox.

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

@ -28,7 +28,7 @@ are applied to Git HTTP requests.
To configure Git HTTP rate limits:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Git HTTP rate limits**.
1. Select **Enable unauthenticated Git HTTP request rate limit**.

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

@ -25,7 +25,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Git LFS Rate Limits**.
1. Select **Enable authenticated Git LFS request rate limit**.

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

@ -20,7 +20,7 @@ DETAILS:
Configure the following call timeouts to make sure that long-running Gitaly calls don't needlessly take up resources. To
configure the call timeouts:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand the **Gitaly timeouts** section.
1. Set each timeout as required.

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

@ -18,7 +18,7 @@ to go for help. You can customize and display this information on the GitLab `/h
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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Help page**.
1. In **Additional text to show on the Help page**, enter the information you want to display on `/help`.
@ -41,7 +41,7 @@ To add a help message to the sign-in page, [customize your sign-in and register
GitLab marketing-related entries are occasionally shown on the Help page. To hide these entries:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Help page**.
1. Select the **Hide marketing-related entries from the Help page** checkbox.
@ -54,7 +54,7 @@ You can specify a custom URL to which users are directed when they:
- Select **Help > Support**.
- Select **See our website for help** on the Help page.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Help page**.
1. In the **Support page URL** field, enter the URL.
@ -64,7 +64,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Preferences**.
1. Expand **Help page**.
1. In the **Documentation pages URL** field, enter the URL.

22
doc/administration/settings/import_and_export_settings.md
View File

@ -18,7 +18,7 @@ Before you can import projects from other systems, you must enable the
[import source](../../user/gitlab_com/index.md#default-import-sources) for that system.
1. Sign in to GitLab as a user with Administrator access level.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Import and export settings** section.
1. Select each of **Import sources** to allow.
@ -30,7 +30,7 @@ To enable the export of
[projects and their data](../../user/project/settings/import_export.md#export-a-project-and-its-data):
1. Sign in to GitLab as a user with Administrator access level.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Import and export settings** section.
1. Scroll to **Project export**.
@ -55,7 +55,7 @@ Migration of groups and projects by direct transfer is disabled by default.
To enable migration of groups and projects by direct transfer:
1. Sign in to GitLab as a user with Administrator access level.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand the **Import and export settings** section.
1. Scroll to **Allow migrating GitLab groups and projects by direct transfer**.
@ -78,7 +78,7 @@ Exports from non-administrators still generate audit events.
To enable silent admin project and group file exports:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**, then expand **Import and export settings**.
1. Scroll to **Silent exports by admins**.
1. Select the **Enabled** checkbox.
@ -89,7 +89,7 @@ To enable silent admin project and group file exports:
To modify the maximum file size for exports in GitLab:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**, then expand **Import and export settings**.
1. Increase or decrease by changing the value in **Maximum export size (MiB)**.
@ -97,7 +97,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Increase or decrease by changing the value in **Maximum import size (MiB)**.
@ -119,7 +119,7 @@ By default, the maximum remote file size for imports from external object storag
To modify this setting:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Increase or decrease by changing the value in **Maximum import remote file size (MiB)**. Set to `0` to set no file size limit.
@ -132,7 +132,7 @@ By default, the maximum download file size for imports by direct transfer is 5 G
To modify this setting:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Increase or decrease by changing the value in **Direct transfer maximum download file size (MiB)**. Set to `0` to set no download file size limit.
@ -155,7 +155,7 @@ Decompressed archive size validation failed.
To modify this setting:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Set another value for **Maximum decompressed file size for archives from imports (MiB)**.
@ -168,7 +168,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Set another value for **Timeout for decompressing archived files (seconds)**.
@ -195,7 +195,7 @@ The default job limit is:
To modify this setting:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > General**.
1. Expand **Import and export settings**.
1. Set another value for **Maximum number of simultaneous import jobs** for the desired importer.

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

@ -14,7 +14,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, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Import and export rate limits**.
1. Change the value of any rate limit. The rate limits are per minute per user, not per IP address.

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

@ -31,7 +31,7 @@ Requests that exceed the limit are logged into `auth.log`.
To set inbound incident management alert limits:
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Settings > Network**.
1. Expand **Incident Management Limits**.
1. Select the **Enable Incident Management inbound alert limit** checkbox.

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

@ -21,4 +21,4 @@ Use **Settings** to control settings across the instance.
To access the **Admin area**:
1. Sign in to your GitLab instance as an administrator.
1. On the left sidebar, at the bottom, select **Admin area**.
1. On the left sidebar, at the bottom, select **Admin**.

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