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 2025-01-10 21:31:26 +00:00
parent 15cc871f89
commit eefff9d8be
191 changed files with 918 additions and 297 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
app/assets/javascripts/diffs/components/tree_list.vue
View File

@ -144,16 +144,28 @@ export default {
currentDiffFileId(hash) {
if (hash) {
this.scrollVirtualScrollerToFileHash(hash);
this.openFileTree(hash);
}
},
},
methods: {
...mapActions('diffs', ['toggleTreeOpen', 'goToFile', 'setRenderTreeList']),
...mapActions('diffs', ['toggleTreeOpen', 'goToFile', 'setRenderTreeList', 'setTreeOpen']),
scrollVirtualScrollerToFileHash(hash) {
const index = this.treeList.findIndex((f) => f.fileHash === hash);
if (index !== -1) {
this.$refs.scroller.scrollToItem(index);
this.$refs.scroller.scrollToItem?.(index);
}
},
openFileTree(hash) {
const file = this.flatFilteredTreeList.find((f) => f.fileHash === hash);
if (file) {
file.path
.split('/')
.slice(0, -1)
.reduce((acc, part) => [...acc, acc.length ? `${acc.at(-1)}/${part}` : part], [])
.forEach((path) => this.setTreeOpen({ path, opened: true }));
}
},
},

4
app/assets/javascripts/diffs/store/actions.js
View File

@ -665,6 +665,10 @@ export const toggleTreeOpen = ({ commit }, path) => {
commit(types.TOGGLE_FOLDER_OPEN, path);
};
export const setTreeOpen = ({ commit }, { path, opened }) => {
commit(types.SET_FOLDER_OPEN, { path, opened });
};
export const setCurrentFileHash = ({ commit }, hash) => {
commit(types.SET_CURRENT_DIFF_FILE, hash);
};

1
app/assets/javascripts/diffs/store/mutation_types.js
View File

@ -21,6 +21,7 @@ export const SET_LINE_DISCUSSIONS_FOR_FILE = 'SET_LINE_DISCUSSIONS_FOR_FILE';
export const TOGGLE_FILE_DISCUSSION_EXPAND = 'TOGGLE_FILE_DISCUSSION_EXPAND';
export const REMOVE_LINE_DISCUSSIONS_FOR_FILE = 'REMOVE_LINE_DISCUSSIONS_FOR_FILE';
export const TOGGLE_FOLDER_OPEN = 'TOGGLE_FOLDER_OPEN';
export const SET_FOLDER_OPEN = 'SET_FOLDER_OPEN';
export const TREE_ENTRY_DIFF_LOADING = 'TREE_ENTRY_DIFF_LOADING';
export const SET_SHOW_TREE_LIST = 'SET_SHOW_TREE_LIST';
export const SET_CURRENT_DIFF_FILE = 'SET_CURRENT_DIFF_FILE';

3
app/assets/javascripts/diffs/store/mutations.js
View File

@ -291,6 +291,9 @@ export default {
[types.TOGGLE_FOLDER_OPEN](state, path) {
state.treeEntries[path].opened = !state.treeEntries[path].opened;
},
[types.SET_FOLDER_OPEN](state, { path, opened }) {
state.treeEntries[path].opened = opened;
},
[types.TREE_ENTRY_DIFF_LOADING](state, { path, loading = true }) {
state.treeEntries[path].diffLoading = loading;
},

4
app/assets/javascripts/diffs/stores/legacy_diffs/actions.js
View File

@ -665,6 +665,10 @@ export function toggleTreeOpen(path) {
this[types.TOGGLE_FOLDER_OPEN](path);
}
export function setTreeOpen({ path, opened }) {
this[types.SET_FOLDER_OPEN]({ path, opened });
}
export function setCurrentFileHash(hash) {
this[types.SET_CURRENT_DIFF_FILE](hash);
}

3
app/assets/javascripts/diffs/stores/legacy_diffs/mutations.js
View File

@ -287,6 +287,9 @@ export default {
[types.TOGGLE_FOLDER_OPEN](path) {
this.treeEntries[path].opened = !this.treeEntries[path].opened;
},
[types.SET_FOLDER_OPEN]({ path, opened }) {
this.treeEntries[path].opened = opened;
},
[types.TREE_ENTRY_DIFF_LOADING]({ path, loading = true }) {
this.treeEntries[path].diffLoading = loading;
},

3
app/assets/javascripts/merge_request_dashboard/components/collapsible_section.vue
View File

@ -12,6 +12,7 @@ export default {
directives: {
GlTooltip: GlTooltipDirective,
},
inject: ['newListsEnabled'],
props: {
title: {
type: String,
@ -68,7 +69,7 @@ export default {
is-collapsible
:collapsed="!open"
:toggle-aria-label="toggleButtonLabel"
:body-class="{ '!gl-mx-0 gl-mb-0': hasMergeRequests }"
:body-class="{ '!gl-mx-0 gl-mb-0': hasMergeRequests || newListsEnabled }"
>
<template #title>
{{ title }}

104
db/click_house/migrate/main/20250109180239_create_siphon_projects.rb Normal file
View File

@ -0,0 +1,104 @@
# frozen_string_literal: true
class CreateSiphonProjects < ClickHouse::Migration
def up
execute <<-SQL
CREATE TABLE IF NOT EXISTS siphon_projects
(
id Int64,
name Nullable(String),
path Nullable(String),
description Nullable(String),
created_at Nullable(DateTime64(6, 'UTC')),
updated_at Nullable(DateTime64(6, 'UTC')),
creator_id Nullable(Int64),
namespace_id Int64,
last_activity_at Nullable(DateTime64(6, 'UTC')),
import_url Nullable(String),
visibility_level Int64 DEFAULT 0,
archived Boolean DEFAULT false,
avatar Nullable(String),
merge_requests_template Nullable(String),
star_count Int64 DEFAULT 0,
merge_requests_rebase_enabled Nullable(Boolean) DEFAULT false,
import_type Nullable(String),
import_source Nullable(String),
approvals_before_merge Int64 DEFAULT 0,
reset_approvals_on_push Nullable(Boolean) DEFAULT true,
merge_requests_ff_only_enabled Nullable(Boolean) DEFAULT false,
issues_template Nullable(String),
mirror Boolean DEFAULT false,
mirror_last_update_at Nullable(DateTime64(6, 'UTC')),
mirror_last_successful_update_at Nullable(DateTime64(6, 'UTC')),
mirror_user_id Nullable(Int64),
shared_runners_enabled Boolean DEFAULT true,
runners_token Nullable(String),
build_allow_git_fetch Boolean DEFAULT true,
build_timeout Int64 DEFAULT 3600,
mirror_trigger_builds Boolean DEFAULT false,
pending_delete Nullable(Boolean) DEFAULT false,
public_builds Boolean DEFAULT true,
last_repository_check_failed Nullable(Boolean),
last_repository_check_at Nullable(DateTime64(6, 'UTC')),
only_allow_merge_if_pipeline_succeeds Boolean DEFAULT false,
has_external_issue_tracker Nullable(Boolean),
repository_storage String DEFAULT 'default',
repository_read_only Nullable(Boolean),
request_access_enabled Boolean DEFAULT true,
has_external_wiki Nullable(Boolean),
ci_config_path Nullable(String),
lfs_enabled Nullable(Boolean),
description_html Nullable(String),
only_allow_merge_if_all_discussions_are_resolved Nullable(Boolean),
repository_size_limit Nullable(Int64),
printing_merge_request_link_enabled Boolean DEFAULT true,
auto_cancel_pending_pipelines Int64 DEFAULT 1,
service_desk_enabled Nullable(Boolean) DEFAULT true,
cached_markdown_version Nullable(Int64),
delete_error Nullable(String),
last_repository_updated_at Nullable(DateTime64(6, 'UTC')),
disable_overriding_approvers_per_merge_request Nullable(Boolean),
storage_version Nullable(Int8),
resolve_outdated_diff_discussions Nullable(Boolean),
remote_mirror_available_overridden Nullable(Boolean),
only_mirror_protected_branches Nullable(Boolean),
pull_mirror_available_overridden Nullable(Boolean),
jobs_cache_index Nullable(Int64),
external_authorization_classification_label Nullable(String),
mirror_overwrites_diverged_branches Nullable(Boolean),
pages_https_only Nullable(Boolean) DEFAULT true,
external_webhook_token Nullable(String),
packages_enabled Nullable(Boolean),
merge_requests_author_approval Nullable(Boolean) DEFAULT false,
pool_repository_id Nullable(Int64),
runners_token_encrypted Nullable(String),
bfg_object_map Nullable(String),
detected_repository_languages Nullable(Boolean),
merge_requests_disable_committers_approval Nullable(Boolean),
require_password_to_approve Nullable(Boolean),
emails_disabled Nullable(Boolean),
max_pages_size Nullable(Int64),
max_artifacts_size Nullable(Int64),
pull_mirror_branch_prefix Nullable(String),
remove_source_branch_after_merge Nullable(Boolean),
marked_for_deletion_at Nullable(Date32),
marked_for_deletion_by_user_id Nullable(Int64),
autoclose_referenced_issues Nullable(Boolean),
suggestion_commit_message Nullable(String),
project_namespace_id Nullable(Int64),
hidden Boolean DEFAULT false,
organization_id Nullable(Int64),
_siphon_replicated_at DateTime64(6, 'UTC') DEFAULT now(),
_siphon_deleted Boolean DEFAULT FALSE
)
ENGINE = ReplacingMergeTree(_siphon_replicated_at, _siphon_deleted)
PRIMARY KEY id
SQL
end
def down
execute <<-SQL
DROP TABLE IF EXISTS siphon_projects
SQL
end
end

2
doc/administration/administer_users.md
View File

@ -11,7 +11,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
Administer and manage users in your self-managed GitLab installation.
Administer and manage users in GitLab Self-Managed.
## User accounts

2
doc/administration/configure.md
View File

@ -11,7 +11,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** Self-managed
Customize and configure your self-managed GitLab installation.
Customize and configure GitLab Self-Managed.
- [Authentication](auth/index.md)
- [CI/CD](../administration/cicd/index.md)

2
doc/administration/diff_limits.md
View File

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Configure the maximum diff size to display on your self-managed GitLab instance."
description: "Configure the maximum diff size to display on GitLab Self-Managed."
---
# Diff limits administration

2
doc/administration/docs_self_host.md
View File

@ -17,7 +17,7 @@ NOTE:
The local help of your instance does not include all the docs (for example, it
doesn't include docs for GitLab Runner or GitLab Operator), and it's not
searchable or browsable. It's intended to only support direct links to specific
pages from within a self-managed GitLab instance.
pages from within your instance.
## Documentation self-hosting options

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

@ -81,11 +81,11 @@ Benefits:
#### Migration to GitLab Dedicated
You can also use Geo to migrate your self-managed GitLab instance to [GitLab Dedicated](../../subscriptions/gitlab_dedicated/index.md). A migration to GitLab Dedicated is similar to an infrastructure migration.
You can also use Geo to migrate GitLab Self-Managed to [GitLab Dedicated](../../subscriptions/gitlab_dedicated/index.md). A migration to GitLab Dedicated is similar to an infrastructure migration.
Benefits:
- Smoother onboarding experience with significantly lower downtime. Your team can continue to use your self-managed GitLab instance while the data migration takes place in the background.
- Smoother onboarding experience with significantly lower downtime. Your team can continue to use GitLab Self-Managed while the data migration takes place in the background.
## What Geo is not designed to address

2
doc/administration/git_protocol.md
View File

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Set and configure Git protocol v2 for your self-managed GitLab instance."
description: "Set and configure Git protocol v2 for GitLab Self-Managed."
---
# Configuring Git Protocol v2

2
doc/administration/index.md
View File

@ -7,7 +7,7 @@ description: 'Learn how to install, configure, update, and maintain your GitLab
# Administer GitLab
Learn how to administer a self-managed GitLab instance.
Learn how to administer GitLab Self-Managed.
| | | |
|--|--|--|

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure a Diagrams.net integration for your self-managed GitLab instance."
description: "Configure a Diagrams.net integration for GitLab Self-Managed."
---
# Diagrams.net
@ -34,7 +34,7 @@ After completing the integration, the diagrams.net editor opens with the URL you
You can set up your own diagrams.net server to generate the diagrams.
It's a required step for users on an offline environment self-managed GitLab installations.
It's a required step for users on an offline installation of GitLab Self-Managed.
For example, to run a diagrams.net container in Docker, run the following command:

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure PlantUML integration with your self-managed GitLab instance."
description: "Configure PlantUML integration with GitLab Self-Managed."
---
# PlantUML

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure Git LFS for your self-managed GitLab instance."
description: "Configure Git LFS for GitLab Self-Managed."
---
# GitLab Git Large File Storage (LFS) Administration

2
doc/administration/moderate_users.md
View File

@ -166,7 +166,7 @@ Prerequisites:
- The user has had no activity in the last 90 days.
To deactivate a user from a self-managed GitLab instance:
To deactivate a user:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Overview > Users**.

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

@ -241,7 +241,7 @@ configuration option in `gitlab.yml`. These metrics are served from the
| `sidekiq_jobs_dead_total` | Counter | 13.7 | Sidekiq dead jobs (jobs that have run out of retries) | `queue`, `boundary`, `external_dependencies`, `feature_category`, `urgency` |
| `sidekiq_redis_requests_total` | Counter | 13.1 | Redis requests during a Sidekiq job execution | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
| `sidekiq_elasticsearch_requests_total` | Counter | 13.1 | Elasticsearch requests during a Sidekiq job execution | `queue`, `boundary`, `external_dependencies`, `feature_category`, `job_status`, `urgency` |
| `sidekiq_jobs_skipped_total` | Counter | 16.2 | Number of jobs being skipped (dropped or deferred) when `drop_sidekiq_jobs` feature flag is enabled or `run_sidekiq_jobs` feature flag is disabled | `worker`, `action` |
| `sidekiq_jobs_skipped_total` | Counter | 16.2 | Number of jobs being skipped (dropped or deferred) when `drop_sidekiq_jobs` feature flag is enabled or `run_sidekiq_jobs` feature flag is disabled | `worker`, `action`, `feature_category`, `reason` |
| `sidekiq_running_jobs` | Gauge | 12.2 | Number of Sidekiq jobs running | `queue`, `boundary`, `external_dependencies`, `feature_category`, `urgency` |
| `sidekiq_concurrency` | Gauge | 12.5 | Maximum number of Sidekiq jobs | |
| `sidekiq_mem_total_bytes` | Gauge | 15.3 | Number of bytes allocated for both objects consuming an object slot and objects that required a malloc'| |

4
doc/administration/monitoring/prometheus/pgbouncer_exporter.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/monitoring/prometheus/postgres_exporter.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/database_load_balancing.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/external.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/external_metrics.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/external_upgrade.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

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

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/moving.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/pgbouncer.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/replication_and_failover.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/replication_and_failover_troubleshooting.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/standalone.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

4
doc/administration/postgresql/upgrading_os.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

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

@ -70,7 +70,7 @@ If you do not meet the use case criteria for self-hosted models, you can use the
GitLab.com AI gateway with default GitLab external vendor LLMs.
The GitLab.com AI gateway is the default Enterprise offering and is not self-hosted. In this configuration,
you connect your self-managed GitLab instance to the GitLab-hosted AI gateway, which
you connect your GitLab Self-Managed instance to the GitLab-hosted AI gateway, which
integrates with external vendor LLM providers (such as Google Vertex or Anthropic).
These LLMs communicate through the [GitLab Cloud Connector](../../development/cloud_connector/index.md),

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure the maximum number of projects users can create on your self-managed GitLab instance. Configure size limits for attachments, pushes, and repository size."
description: "Configure the maximum number of projects users can create on GitLab Self-Managed. Configure size limits for attachments, pushes, and repository size."
---
# Account and limit settings

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Define limits for deprecated APIs on your self-managed GitLab instance."
description: "Define limits for deprecated APIs on GitLab Self-Managed."
---
# Deprecated API rate limits

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Configure rate limits for the repository files API on your self-managed GitLab instance."
description: "Configure rate limits for the repository files API on GitLab Self-Managed."
---
# Rate limits on Repository files API

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Configure rate limits on Git HTTP requests to your self-managed GitLab instance."
description: "Configure rate limits on Git HTTP requests to GitLab Self-Managed."
---
# Rate limits on Git HTTP

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Configure rate limits for Git LFS on your self-managed GitLab instance."
description: "Configure rate limits for Git LFS on GitLab Self-Managed."
---
# Rate limits on Git LFS

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure a collection of file templates available for all projects on your self-managed GitLab instance."
description: "Configure a collection of file templates available for all projects on GitLab Self-Managed."
---
# Instance template repository

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

@ -56,7 +56,7 @@ To resolve this issue, disable the **Jira Connect Proxy URL** setting.
1. Clear the **Jira Connect Proxy URL** text box.
1. Select **Save changes**.
If the issue persists, verify that your self-managed GitLab instance can connect to
If the issue persists, verify that your instance can connect to
`connect-install-keys.atlassian.com` to get the public key from Atlassian.
To test connectivity, run the following command:
@ -67,13 +67,13 @@ curl --head "https://connect-install-keys.atlassian.com"
## Data sync fails with `Invalid JWT`
If the GitLab for Jira Cloud app continuously fails to sync data from a self-managed GitLab instance,
If the GitLab for Jira Cloud app continuously fails to sync data from your instance,
a secret token might be outdated. Atlassian can send new secret tokens to GitLab.
If GitLab fails to process or store these tokens, an `Invalid JWT` error occurs.
To resolve this issue on your self-managed GitLab instance:
To resolve this issue:
- Confirm your self-managed GitLab instance is publicly available to:
- Confirm the instance is publicly available to:
- GitLab.com (if you [installed the app from the official Atlassian Marketplace listing](jira_cloud_app.md#install-the-gitlab-for-jira-cloud-app-from-the-atlassian-marketplace)).
- Jira Cloud (if you [installed the app manually](jira_cloud_app.md#install-the-gitlab-for-jira-cloud-app-manually)).
- Ensure the token request sent to the `/-/jira_connect/events/installed` endpoint when you install the app is accessible from Jira.
@ -83,7 +83,7 @@ To resolve this issue on your self-managed GitLab instance:
curl --include --request POST "https://gitlab.example.com/-/jira_connect/events/installed"
```
- If your self-managed GitLab instance has [SSL configured](https://docs.gitlab.com/omnibus/settings/ssl/), check your
- If your instance has [SSL configured](https://docs.gitlab.com/omnibus/settings/ssl/), check your
[certificates are valid and publicly trusted](https://docs.gitlab.com/omnibus/settings/ssl/ssl_troubleshooting.html#useful-openssl-debugging-commands).
Depending on how you installed the app, you might want to check the following:

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Configure limits on the number of single push events your self-managed GitLab instance will allow."
description: "Configure limits on the number of single push events your instance will allow."
---
# Push event activities limit and bulk push events

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
description: "Configure rate limits on Git SSH operations on your self-managed GitLab instance."
description: "Configure rate limits on Git SSH operations on GitLab Self-Managed."
---
# Rate limits on Git SSH operations

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

@ -2,7 +2,7 @@
stage: Create
group: Source Code
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments"
description: "Control project visibility, creation, retention, and deletion on your self-managed GitLab instance."
description: "Control project visibility, creation, retention, and deletion on GitLab Self-Managed."
---
# Control access and visibility

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

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Operations
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

2
doc/administration/user_settings.md
View File

@ -14,7 +14,7 @@ You can modify settings for every user in your GitLab instance.
## Prerequisites
- You must be an administrator of a self-managed GitLab instance.
- You must be an administrator of GitLab Self-Managed.
## Prevent users from creating top-level groups

4
doc/api/database_migrations.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
---

2
doc/api/graphql/getting_started.md
View File

@ -34,7 +34,7 @@ For most people, using GraphiQL will be the easiest way to explore the GitLab Gr
You can either use GraphiQL:
- [On GitLab.com](https://gitlab.com/-/graphql-explorer).
- On your self-managed GitLab instance on `https://<your-gitlab-site.com>/-/graphql-explorer`.
- On GitLab Self-Managed on `https://<your-gitlab-site.com>/-/graphql-explorer`.
Sign in to GitLab first to authenticate the requests with your GitLab account.

2
doc/api/graphql/index.md
View File

@ -33,7 +33,7 @@ The GitLab GraphQL API endpoint is located at `/api/graphql`.
Explore the GraphQL API using the interactive GraphQL explorer, either:
- [On GitLab.com](https://gitlab.com/-/graphql-explorer).
- On your self-managed GitLab instance on `https://<your-gitlab-site.com>/-/graphql-explorer`.
- On GitLab Self-Managed on `https://<your-gitlab-site.com>/-/graphql-explorer`.
For more information, see [GraphiQL](getting_started.md#graphiql).

32
doc/api/graphql/reference/index.md
View File

@ -12051,6 +12051,29 @@ The edge type for [`AiUserMetrics`](#aiusermetrics).
| <a id="aiusermetricsedgecursor"></a>`cursor` | [`String!`](#string) | A cursor for use in pagination. |
| <a id="aiusermetricsedgenode"></a>`node` | [`AiUserMetrics`](#aiusermetrics) | The item at the end of the edge. |
#### `AiXrayReportConnection`
The connection type for [`AiXrayReport`](#aixrayreport).
##### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="aixrayreportconnectionedges"></a>`edges` | [`[AiXrayReportEdge]`](#aixrayreportedge) | A list of edges. |
| <a id="aixrayreportconnectionnodes"></a>`nodes` | [`[AiXrayReport]`](#aixrayreport) | A list of nodes. |
| <a id="aixrayreportconnectionpageinfo"></a>`pageInfo` | [`PageInfo!`](#pageinfo) | Information to aid in pagination. |
#### `AiXrayReportEdge`
The edge type for [`AiXrayReport`](#aixrayreport).
##### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="aixrayreportedgecursor"></a>`cursor` | [`String!`](#string) | A cursor for use in pagination. |
| <a id="aixrayreportedgenode"></a>`node` | [`AiXrayReport`](#aixrayreport) | The item at the end of the edge. |
#### `AlertManagementAlertConnection`
The connection type for [`AlertManagementAlert`](#alertmanagementalert).
@ -19116,6 +19139,14 @@ Pre-aggregated per-user metrics for GitLab Code Suggestions and GitLab Duo Chat.
| <a id="aiusermetricsduochatinteractionscount"></a>`duoChatInteractionsCount` | [`Int`](#int) | Number of user interactions with GitLab Duo Chat. |
| <a id="aiusermetricsuser"></a>`user` | [`UserCore!`](#usercore) | User metrics. |
### `AiXrayReport`
#### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="aixrayreportlanguage"></a>`language` | [`String!`](#string) | Language of the x-ray report. |
### `AlertManagementAlert`
Describes an alert from the project's Alert Management.
@ -31888,6 +31919,7 @@ Project-level settings for product analytics provider.
| <a id="projectagentconfigurations"></a>`agentConfigurations` | [`AgentConfigurationConnection`](#agentconfigurationconnection) | Agent configurations defined by the project. (see [Connections](#connections)) |
| <a id="projectaiagents"></a>`aiAgents` **{warning-solid}** | [`AiAgentConnection`](#aiagentconnection) | **Introduced** in GitLab 16.9. **Status**: Experiment. Ai Agents for the project. |
| <a id="projectaiusagedata"></a>`aiUsageData` **{warning-solid}** | [`AiUsageData`](#aiusagedata) | **Introduced** in GitLab 17.5. **Status**: Experiment. AI-related data. |
| <a id="projectaixrayreports"></a>`aiXrayReports` **{warning-solid}** | [`AiXrayReportConnection!`](#aixrayreportconnection) | **Introduced** in GitLab 17.8. **Status**: Experiment. X-ray reports of the project. |
| <a id="projectallowmergeonskippedpipeline"></a>`allowMergeOnSkippedPipeline` | [`Boolean`](#boolean) | If `only_allow_merge_if_pipeline_succeeds` is true, indicates if merge requests of the project can also be merged with skipped jobs. |
| <a id="projectallowedcustomstatuses"></a>`allowedCustomStatuses` **{warning-solid}** | [`WorkItemWidgetCustomStatusConnection`](#workitemwidgetcustomstatusconnection) | **Introduced** in GitLab 17.8. **Status**: Experiment. Allowed custom statuses for the project. |
| <a id="projectallowsmultiplemergerequestassignees"></a>`allowsMultipleMergeRequestAssignees` | [`Boolean!`](#boolean) | Project allows assigning multiple users to a merge request. |

2
doc/ci/environments/deployments.md
View File

@ -156,7 +156,7 @@ When you work with deployments, you might encounter the following issues.
GitLab [deletes old deployment refs](#archive-old-deployments)
to keep your Git repository performant.
If you have to restore archived Git-refs, ask an administrator of your self-managed GitLab instance
If you have to restore archived Git-refs on GitLab Self-Managed, ask an administrator
to execute the following command on Rails console:
```ruby

2
doc/ci/examples/index.md
View File

@ -108,7 +108,7 @@ DETAILS:
**Tier:** Premium, Ultimate
**Offering:** Self-managed, GitLab Dedicated
You can add custom examples and templates to your self-managed GitLab instance.
You can add custom examples and templates to your instance.
Your GitLab administrator can [designate an instance template repository](../../administration/settings/instance_template_repository.md)
that contains examples and templates specific to your organization.

2
doc/ci/runners/configure_runners.md
View File

@ -29,7 +29,7 @@ Prerequisites:
- You must be an administrator.
You can override the job timeout for instance runners on self-managed GitLab installations only.
You can override the job timeout for instance runners on GitLab Self-Managed.
On GitLab.com, you cannot override the job timeout for GitLab hosted instance runners and must use the [project defined timeout](../pipelines/settings.md#set-a-limit-for-how-long-jobs-can-run) instead.

6
doc/ci/runners/runners_scope.md
View File

@ -241,7 +241,7 @@ Prerequisites:
- You must have the Owner role for the group.
You can create a group runner for your self-managed GitLab instance or for GitLab.com.
You can create a group runner for GitLab Self-Managed or for GitLab.com.
When you create a runner, it is assigned a runner authentication token that you use to register it.
The runner uses the token to authenticate with GitLab when it picks up jobs from the job queue.
@ -306,7 +306,7 @@ Prerequisites:
- You must have the Maintainer or Owner role for the group.
You can view all runners for a group and its subgroups and projects.
You can do this for your self-managed GitLab instance or for GitLab.com.
You can do this for GitLab Self-Managed or for GitLab.com.
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Build > Runners**.
@ -444,7 +444,7 @@ Prerequisites:
- You must have the Maintainer role for the project.
You can create a project runner for your self-managed GitLab instance or for GitLab.com. When you create a runner,
You can create a project runner for GitLab Self-Managed or for GitLab.com. When you create a runner,
it is assigned a runner authentication token that you use to register to the runner. The runner uses the token to
authenticate with GitLab when it picks up jobs from the job queue.

4
doc/development/database/add_foreign_key_to_existing_column.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/adding_database_indexes.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/avoiding_downtime_in_migrations.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/batched_background_migrations.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: "See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines"
---

4
doc/development/database/batching_best_practices.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/ci_mirrored_tables.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/clickhouse_within_gitlab.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/gitlab_activity_data.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/index.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/merge_request_analytics.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/optimization.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/clickhouse/tiered_storage.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

2
doc/development/database/client_side_connection_pool.md
View File

@ -1,5 +1,5 @@
---
stage: Data Stores
stage: Data Access
group: Database
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/constraint_naming_convention.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/creating_enums.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_debugging.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_dictionary.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

7
doc/development/database/database_lab.md
View File

@ -1,6 +1,9 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
type: reference, howto
discretionary: yes
description: Database access for engineers and related parties.
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_lab_pgai.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_migration_pipeline.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_query_comments.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/database_reviewer_guidelines.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/db_dump.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/dbcheck-migrations-job.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

2
doc/development/database/dbmigrate_multi_version_upgrade_job.md
View File

@ -1,5 +1,5 @@
---
stage: Data Stores
stage: Data Access
group: Database
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

2
doc/development/database/deduplicate_database_records.md
View File

@ -1,5 +1,5 @@
---
stage: Data Stores
stage: Data Access
group: Database
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/deleting_migrations.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

2
doc/development/database/efficient_in_operator_queries.md
View File

@ -1,5 +1,5 @@
---
stage: Data Stores
stage: Data Access
group: Database
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/foreign_keys.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/hash_indexes.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/index.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/insert_into_tables_in_batches.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
description: "Sometimes it is necessary to store large amounts of records at once, which can be inefficient
when iterating collections and performing individual `save`s. With the arrival of `insert_all`

4
doc/development/database/iterating_tables_in_batches.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/keyset_pagination.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/layout_and_access_patterns.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/load_balancing.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/loose_foreign_keys.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/maintenance_operations.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/migration_ordering.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

2
doc/development/database/migrations_for_multiple_databases.md
View File

@ -1,5 +1,5 @@
---
stage: Data Stores
stage: Data Access
group: Database
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/new_database_migration_version.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/not_null_constraints.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/offset_pagination_optimization.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/ordering_table_columns.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/pagination_guidelines.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

4
doc/development/database/pagination_performance_guidelines.md
View File

@ -1,6 +1,6 @@
---
stage: Data Stores
group: Database
stage: Data Access
group: Database Frameworks
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---

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