Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
c3ccd2fdf1
commit
eaa1d6fdd7
|
|
@ -140,9 +140,9 @@ export default {
|
|||
default: '',
|
||||
},
|
||||
computeMinutes: {
|
||||
type: String,
|
||||
type: Number,
|
||||
required: false,
|
||||
default: '',
|
||||
default: 0,
|
||||
},
|
||||
yamlErrors: {
|
||||
type: String,
|
||||
|
|
@ -315,7 +315,7 @@ export default {
|
|||
return cancelable && userPermissions.updatePipeline;
|
||||
},
|
||||
showComputeMinutes() {
|
||||
return this.isFinished && this.computeMinutes !== '0.0';
|
||||
return this.isFinished && this.computeMinutes;
|
||||
},
|
||||
},
|
||||
methods: {
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ export const createPipelineDetailsHeaderApp = (elSelector, apolloProvider, graph
|
|||
props: {
|
||||
name,
|
||||
totalJobs,
|
||||
computeMinutes,
|
||||
computeMinutes: Number(computeMinutes),
|
||||
yamlErrors,
|
||||
failureReason,
|
||||
refText,
|
||||
|
|
|
|||
|
|
@ -41,6 +41,12 @@ export default {
|
|||
shouldShowAlert() {
|
||||
return this.errorMessage && !this.isAlertDismissed;
|
||||
},
|
||||
hasCvsSection() {
|
||||
return (
|
||||
this.glFeatures.dependencyScanningOnAdvisoryIngestion &&
|
||||
!this.glFeatures.globalDependencyScanningOnAdvisoryIngestion
|
||||
);
|
||||
},
|
||||
},
|
||||
methods: {
|
||||
reportError(error) {
|
||||
|
|
@ -80,7 +86,7 @@ export default {
|
|||
</script>
|
||||
|
||||
<template>
|
||||
<div v-if="glFeatures.dependencyScanningOnAdvisoryIngestion">
|
||||
<div v-if="hasCvsSection">
|
||||
<h4 class="gl-font-base gl-m-0 gl-mt-6">
|
||||
{{ $options.i18n.title }}
|
||||
<gl-badge
|
||||
|
|
|
|||
|
|
@ -158,36 +158,6 @@
|
|||
}
|
||||
}
|
||||
|
||||
@include media-breakpoint-down(xs) {
|
||||
.event-item {
|
||||
padding-left: 0;
|
||||
|
||||
.event-user-info {
|
||||
margin-bottom: $gl-padding-4;
|
||||
}
|
||||
|
||||
.event-title {
|
||||
white-space: normal;
|
||||
overflow: visible;
|
||||
max-width: 100%;
|
||||
}
|
||||
|
||||
.system-note-image {
|
||||
display: none;
|
||||
}
|
||||
|
||||
.event-body {
|
||||
margin-top: $gl-padding-4;
|
||||
margin-right: 0;
|
||||
padding-left: 0;
|
||||
}
|
||||
|
||||
.event-item-timestamp {
|
||||
display: none;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// hide event scope (namespace + project) where it is not necessary
|
||||
.project-activity {
|
||||
.event-scope {
|
||||
|
|
|
|||
|
|
@ -1171,3 +1171,17 @@ $system-note-icon-m-left: $avatar-m-left + $icon-size-diff / $avatar-m-ratio;
|
|||
padding: $gl-padding;
|
||||
}
|
||||
}
|
||||
|
||||
.project-activity-item:not(:last-of-type) {
|
||||
position: relative;
|
||||
|
||||
&::before {
|
||||
// Avatar width is 32px, connecting line width is 2px.
|
||||
// To center the line relatively to the avatar it should be positioned 15px from the left:
|
||||
// (32px (avatar size) - 2px (line thickness)) / 2 = 15px
|
||||
// stylelint-disable length-zero-no-unit
|
||||
@include vertical-line(0px, 15px);
|
||||
top: auto; // Override top to auto align
|
||||
background: var(--gray-50, $gray-50);
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -601,7 +601,11 @@ class Projects::MergeRequestsController < Projects::MergeRequests::ApplicationCo
|
|||
when :parsed
|
||||
render json: Gitlab::Json.dump(report_comparison[:data]), status: :ok
|
||||
when :error
|
||||
render json: { status_reason: report_comparison[:status_reason] }, status: :bad_request
|
||||
render json: {
|
||||
errors: [report_comparison[:status_reason]],
|
||||
status_reason: report_comparison[:status_reason]
|
||||
},
|
||||
status: :bad_request
|
||||
else
|
||||
raise "Failed to build comparison response as comparison yielded unknown status '#{report_comparison[:status]}'"
|
||||
end
|
||||
|
|
|
|||
|
|
@ -59,11 +59,13 @@ module AvatarsHelper
|
|||
end
|
||||
|
||||
def author_avatar(commit_or_event, options = {})
|
||||
css_class = options[:css_class] || "gl-display-none gl-sm-display-inline-block"
|
||||
|
||||
user_avatar(options.merge({
|
||||
user: commit_or_event.author,
|
||||
user_name: commit_or_event.author_name,
|
||||
user_email: commit_or_event.author_email,
|
||||
css_class: 'd-none d-sm-inline-block'
|
||||
css_class: css_class
|
||||
}))
|
||||
end
|
||||
|
||||
|
|
|
|||
|
|
@ -309,14 +309,14 @@ module EventsHelper
|
|||
base_class = 'system-note-image'
|
||||
|
||||
classes = current_path?('users#activity') ? "#{event.action_name.parameterize}-icon gl-rounded-full gl-bg-gray-50 gl-line-height-0" : "user-avatar"
|
||||
content = current_path?('users#activity') ? icon_for_event(event.action_name, size: 14) : author_avatar(event, size: 32)
|
||||
content = current_path?('users#activity') ? icon_for_event(event.action_name, size: 14) : author_avatar(event, size: 32, css_class: 'gl-display-inline-block')
|
||||
|
||||
tag.div(class: "#{base_class} #{classes}") { content }
|
||||
end
|
||||
|
||||
def inline_event_icon(event)
|
||||
unless current_path?('users#activity')
|
||||
content_tag :span, class: "system-note-image-inline d-none d-sm-flex gl-mr-2 #{event.action_name.parameterize}-icon align-self-center" do
|
||||
content_tag :span, class: "system-note-image-inline gl-display-flex gl-mr-2 #{event.action_name.parameterize}-icon align-self-center" do
|
||||
next design_event_icon(event.action, size: 14) if event.design?
|
||||
|
||||
icon_for_event(event.action_name, size: 14)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
- event = event.present
|
||||
|
||||
- if event.visible_to_user?(current_user)
|
||||
.event-item{ class: current_path?('users#activity') ? 'user-profile-activity gl-border-bottom-0 gl-pl-7! gl-pb-3' : '' }
|
||||
.event-item.gl-border-bottom-0.gl-pb-3{ class: current_path?('users#activity') ? 'gl-pl-7!' : 'project-activity-item' }
|
||||
.event-item-timestamp.gl-font-sm
|
||||
#{time_ago_with_tooltip(event.created_at)}
|
||||
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/427762
|
|||
milestone: '16.5'
|
||||
type: development
|
||||
group: group::environments
|
||||
default_enabled: false
|
||||
default_enabled: true
|
||||
|
|
|
|||
|
|
@ -8,6 +8,64 @@ def doc_path_to_url(path)
|
|||
path.sub("doc/", "https://docs.gitlab.com/ee/").sub("index.md", "").sub(".md", "/")
|
||||
end
|
||||
|
||||
docs_paths_to_review = helper.changes_by_category[:docs]
|
||||
|
||||
# Some docs do not need a review from a Technical Writer.
|
||||
# In these cases, we'll output a message specific to the section.
|
||||
sections_with_no_tw_review = {
|
||||
'doc/solutions' => [],
|
||||
'doc/development' => []
|
||||
}.freeze
|
||||
|
||||
# One exception to the exceptions above: Technical Writing docs should get a TW review.
|
||||
TW_DOCS_PATH = 'doc/development/documentation'
|
||||
|
||||
docs_paths_to_review.reject! do |doc|
|
||||
section_with_no_tw_review = sections_with_no_tw_review.keys.find { |skip_path| doc.start_with?(skip_path) && !doc.start_with?(TW_DOCS_PATH) }
|
||||
next unless section_with_no_tw_review
|
||||
|
||||
sections_with_no_tw_review[section_with_no_tw_review] << doc
|
||||
|
||||
true
|
||||
end
|
||||
|
||||
SOLUTIONS_LABELS = %w[Solutions].freeze
|
||||
DEVELOPMENT_LABELS = ['docs::improvement', 'development guidelines'].freeze
|
||||
|
||||
def no_tw_review_label_message(labels)
|
||||
helper.labels_to_add.concat(%w[documentation type::maintenance maintenance::refactor] + labels)
|
||||
|
||||
'You do not need tech writer review.'
|
||||
end
|
||||
|
||||
SOLUTIONS_MESSAGE = <<~MSG.freeze
|
||||
This MR contains docs in the /solutions directory and should be reviewed by a Solutions Architect approver. #{no_tw_review_label_message(SOLUTIONS_LABELS)}
|
||||
MSG
|
||||
|
||||
DEVELOPMENT_MESSAGE = <<~MSG.freeze
|
||||
This MR contains docs in the /development directory. Any Maintainer, other than the author, can merge. #{no_tw_review_label_message(DEVELOPMENT_LABELS)}
|
||||
MSG
|
||||
|
||||
# For regular pages, prompt for a TW review
|
||||
DOCS_UPDATE_SHORT_MESSAGE = <<~MSG
|
||||
This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is **recommended**. Reviews can happen after you merge.
|
||||
MSG
|
||||
|
||||
DOCS_UPDATE_LONG_MESSAGE = <<~MSG.freeze
|
||||
## Documentation review
|
||||
|
||||
The following files require a review from a technical writer:
|
||||
|
||||
* #{docs_paths_to_review.map { |path| "`#{path}` ([Link to current live version](#{doc_path_to_url(path)}))" }.join("\n* ")}
|
||||
|
||||
The review does not need to block merging this merge request. See the:
|
||||
|
||||
- [Metadata for the `*.md` files](https://docs.gitlab.com/ee/development/documentation/#metadata) that you've changed. The first few lines of each `*.md` file identify the stage and group most closely associated with your docs change.
|
||||
- The [Technical Writer assigned](https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments) for that stage and group.
|
||||
- [Documentation workflows](https://docs.gitlab.com/ee/development/documentation/workflow.html) for information on when to assign a merge request for review.
|
||||
MSG
|
||||
|
||||
# Documentation should be updated for feature::addition and feature::enhancement
|
||||
DOCUMENTATION_UPDATE_MISSING = <<~MSG
|
||||
~"feature::addition" and ~"feature::enhancement" merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the [Technical Writer counterpart](https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments).
|
||||
|
||||
|
|
@ -17,36 +75,13 @@ For more information, see:
|
|||
- The [definition of done](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#definition-of-done) documentation.
|
||||
MSG
|
||||
|
||||
docs_paths_to_review = helper.changes_by_category[:docs]
|
||||
# Output messages
|
||||
warn(DOCUMENTATION_UPDATE_MISSING) if docs_paths_to_review.empty? && feature_mr?
|
||||
|
||||
# Some docs do not need a review from a technical writer
|
||||
SKIP_TW_REVIEW_PATHS = ['doc/solutions'].freeze
|
||||
message(SOLUTIONS_MESSAGE) if sections_with_no_tw_review["doc/solutions"].any?
|
||||
message(DEVELOPMENT_MESSAGE) if sections_with_no_tw_review["doc/development"].any?
|
||||
|
||||
docs_paths_to_review.delete_if do |item|
|
||||
SKIP_TW_REVIEW_PATHS.any? { |skip_path| item.start_with?(skip_path) }
|
||||
unless docs_paths_to_review.empty?
|
||||
message(DOCS_UPDATE_SHORT_MESSAGE)
|
||||
markdown(DOCS_UPDATE_LONG_MESSAGE)
|
||||
end
|
||||
|
||||
# Documentation should be updated for feature::addition and feature::enhancement
|
||||
if docs_paths_to_review.empty?
|
||||
warn(DOCUMENTATION_UPDATE_MISSING) if feature_mr?
|
||||
|
||||
return
|
||||
end
|
||||
|
||||
message 'This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is **recommended**. Reviews can happen after you merge.'
|
||||
|
||||
return unless helper.ci?
|
||||
|
||||
markdown(<<~MARKDOWN)
|
||||
## Documentation review
|
||||
|
||||
The following files require a review from a technical writer:
|
||||
|
||||
* #{docs_paths_to_review.map { |path| "`#{path}` ([Link to current live version](#{doc_path_to_url(path)}))" }.join("\n* ")}
|
||||
|
||||
The review does not need to block merging this merge request. See the:
|
||||
|
||||
- [Metadata for the `*.md` files](https://docs.gitlab.com/ee/development/documentation/#metadata) that you've changed. The first few lines of each `*.md` file identify the stage and group most closely associated with your docs change.
|
||||
- The [Technical Writer assigned](https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments) for that stage and group.
|
||||
- [Documentation workflows](https://docs.gitlab.com/ee/development/documentation/workflow.html) for information on when to assign a merge request for review.
|
||||
MARKDOWN
|
||||
|
|
|
|||
|
|
@ -0,0 +1,20 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
class DropIndexUsersRequireTwoFactorAuthenticationFromGroupFalse < Gitlab::Database::Migration[2.2]
|
||||
milestone '16.7'
|
||||
|
||||
disable_ddl_transaction!
|
||||
|
||||
TABLE_NAME = :users
|
||||
INDEX_NAME = :index_users_require_two_factor_authentication_from_group_false
|
||||
|
||||
def up
|
||||
remove_concurrent_index_by_name TABLE_NAME, INDEX_NAME
|
||||
end
|
||||
|
||||
def down
|
||||
add_concurrent_index TABLE_NAME, :require_two_factor_authentication_from_group,
|
||||
where: 'require_two_factor_authentication_from_group = FALSE',
|
||||
name: INDEX_NAME
|
||||
end
|
||||
end
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
class DropIndexUsersRequireTwoFactorAuthenticationFromGroup < Gitlab::Database::Migration[2.2]
|
||||
milestone '16.7'
|
||||
|
||||
disable_ddl_transaction!
|
||||
|
||||
TABLE_NAME = :users
|
||||
INDEX_NAME = :index_users_on_require_two_factor_authentication_from_group
|
||||
|
||||
def up
|
||||
remove_concurrent_index_by_name TABLE_NAME, INDEX_NAME
|
||||
end
|
||||
|
||||
def down
|
||||
add_concurrent_index TABLE_NAME, :require_two_factor_authentication_from_group,
|
||||
where: 'require_two_factor_authentication_from_group = TRUE',
|
||||
name: INDEX_NAME
|
||||
end
|
||||
end
|
||||
|
|
@ -0,0 +1 @@
|
|||
9043a1a0202742ba8c35b33fb483b6bb3c47a1df22da2d4a285a326bf09fa409
|
||||
|
|
@ -0,0 +1 @@
|
|||
0c3790315f5d765c4cd13b5c7029886cf91edf1cce6e401c6c511dd9063a90c0
|
||||
|
|
@ -34746,8 +34746,6 @@ CREATE INDEX index_users_on_name_trigram ON users USING gin (name gin_trgm_ops);
|
|||
|
||||
CREATE INDEX index_users_on_public_email_excluding_null_and_empty ON users USING btree (public_email) WHERE (((public_email)::text <> ''::text) AND (public_email IS NOT NULL));
|
||||
|
||||
CREATE INDEX index_users_on_require_two_factor_authentication_from_group ON users USING btree (require_two_factor_authentication_from_group) WHERE (require_two_factor_authentication_from_group = true);
|
||||
|
||||
CREATE UNIQUE INDEX index_users_on_reset_password_token ON users USING btree (reset_password_token);
|
||||
|
||||
CREATE INDEX index_users_on_state_and_user_type ON users USING btree (state, user_type);
|
||||
|
|
@ -34772,8 +34770,6 @@ CREATE INDEX index_users_ops_dashboard_projects_on_project_id ON users_ops_dashb
|
|||
|
||||
CREATE UNIQUE INDEX index_users_ops_dashboard_projects_on_user_id_and_project_id ON users_ops_dashboard_projects USING btree (user_id, project_id);
|
||||
|
||||
CREATE INDEX index_users_require_two_factor_authentication_from_group_false ON users USING btree (require_two_factor_authentication_from_group) WHERE (require_two_factor_authentication_from_group = false);
|
||||
|
||||
CREATE INDEX index_users_security_dashboard_projects_on_user_id ON users_security_dashboard_projects USING btree (user_id);
|
||||
|
||||
CREATE INDEX index_users_star_projects_on_project_id ON users_star_projects USING btree (project_id);
|
||||
|
|
|
|||
|
|
@ -203,7 +203,7 @@ successfully, you must replicate their data using some other means.
|
|||
|[Container registry](../../packages/container_registry.md) | **Yes** (12.3)<sup>1</sup> | **Yes** (15.10) | **Yes** (12.3)<sup>1</sup> | **Yes** (15.10) | See [instructions](container_registry.md) to set up the container registry replication. |
|
||||
|[Terraform Module Registry](../../../user/packages/terraform_module_registry/index.md) | **Yes** (14.0) | **Yes** (14.0) | [**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551) | [**Yes** (16.4)](object_storage.md) | Behind feature flag `geo_package_file_replication`, enabled by default. |
|
||||
|[Project designs repository](../../../user/project/issues/design_management.md) | **Yes** (12.7) | **Yes** (16.1) | Not applicable | Not applicable | Designs also require replication of LFS objects and Uploads. |
|
||||
|[Package Registry](../../../user/packages/package_registry/index.md) | **Yes** (13.2) | **Yes** (13.10) | [**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551) | [**Yes** (16.4)](object_storage.md) | Behind feature flag `geo_package_file_replication`, enabled by default. |
|
||||
|[Package registry](../../../user/packages/package_registry/index.md) | **Yes** (13.2) | **Yes** (13.10) | [**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551) | [**Yes** (16.4)](object_storage.md) | Behind feature flag `geo_package_file_replication`, enabled by default. |
|
||||
|[Versioned Terraform State](../../terraform_state.md) | **Yes** (13.5) | **Yes** (13.12) | [**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551) | [**Yes** (16.4)](object_storage.md) | Replication is behind the feature flag `geo_terraform_state_version_replication`, enabled by default. Verification was behind the feature flag `geo_terraform_state_version_verification`, which was removed in 14.0. |
|
||||
|[External merge request diffs](../../merge_request_diffs.md) | **Yes** (13.5) | **Yes** (14.6) | [**Yes** (15.1)](https://gitlab.com/groups/gitlab-org/-/epics/5551) | [**Yes** (16.4)](object_storage.md) | Replication is behind the feature flag `geo_merge_request_diff_replication`, enabled by default. Verification was behind the feature flag `geo_merge_request_diff_verification`, removed in 14.7.|
|
||||
|[Versioned snippets](../../../user/snippets.md#versioned-snippets) | [**Yes** (13.7)](https://gitlab.com/groups/gitlab-org/-/epics/2809) | [**Yes** (14.2)](https://gitlab.com/groups/gitlab-org/-/epics/2810) | Not applicable | Not applicable | Verification was implemented behind the feature flag `geo_snippet_repository_verification` in 13.11, and the feature flag was removed in 14.2. |
|
||||
|
|
|
|||
|
|
@ -839,7 +839,7 @@ This behavior affects only the following data types through GitLab 14.6:
|
|||
|
||||
| Data type | From version |
|
||||
| ------------------------ | ------------ |
|
||||
| Package Registry | 13.10 |
|
||||
| Package registry | 13.10 |
|
||||
| CI Pipeline Artifacts | 13.11 |
|
||||
| Terraform State Versions | 13.12 |
|
||||
| Infrastructure Registry (renamed to Terraform Module Registry in GitLab 15.11) | 14.0 |
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ Depending on which limits you have configured, you can see:
|
|||
- SSH host keys information
|
||||
- CI/CD limits
|
||||
- GitLab Pages limits
|
||||
- Package Registry limits
|
||||
- Package registry limits
|
||||
- Rate limits
|
||||
- Size limits
|
||||
|
||||
|
|
@ -88,10 +88,10 @@ Read more about [protected path rate limits](settings/protected_paths.md).
|
|||
|
||||
- **Default rate limit**: After 10 requests, the client must wait 60 seconds before trying again.
|
||||
|
||||
### Package Registry
|
||||
### Package registry
|
||||
|
||||
This setting limits the request rate on the Packages API per user or IP. For more information, see
|
||||
[Package Registry Rate Limits](settings/package_registry_rate_limits.md).
|
||||
[package registry rate limits](settings/package_registry_rate_limits.md).
|
||||
|
||||
- **Default rate limit**: Disabled by default.
|
||||
|
||||
|
|
@ -1052,11 +1052,11 @@ individual push events or a bulk push event are created.
|
|||
|
||||
More information can be found in the [Push event activities limit and bulk push events documentation](settings/push_event_activities_limit.md).
|
||||
|
||||
## Package Registry Limits
|
||||
## Package registry limits
|
||||
|
||||
### File Size Limits
|
||||
### File size limits
|
||||
|
||||
The default maximum file size for a package that's uploaded to the [GitLab Package Registry](../user/packages/package_registry/index.md) varies by format:
|
||||
The default maximum file size for a package that's uploaded to the [GitLab package registry](../user/packages/package_registry/index.md) varies by format:
|
||||
|
||||
- Conan: 3 GB
|
||||
- Generic: 5 GB
|
||||
|
|
@ -1105,7 +1105,7 @@ Set the limit to `0` to allow any file size.
|
|||
|
||||
### Package versions returned
|
||||
|
||||
When asking for versions of a given NuGet package name, the GitLab Package Registry returns a maximum of 300 versions.
|
||||
When asking for versions of a given NuGet package name, the GitLab package registry returns a maximum of 300 versions.
|
||||
|
||||
## Dependency Proxy Limits
|
||||
|
||||
|
|
|
|||
|
|
@ -166,9 +166,9 @@ Terraform integration depends on running CI pipelines, hence it is blocked.
|
|||
|
||||
`docker push` fails with this error: `denied: requested access to the resource is denied`, but `docker pull` works.
|
||||
|
||||
### Package Registry
|
||||
### Package registry
|
||||
|
||||
Package Registry allows you to install but not publish packages.
|
||||
Package registry allows you to install but not publish packages.
|
||||
|
||||
### Background jobs
|
||||
|
||||
|
|
|
|||
|
|
@ -4,15 +4,15 @@ group: Package Registry
|
|||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# GitLab Package Registry administration **(FREE SELF)**
|
||||
# GitLab package registry administration **(FREE SELF)**
|
||||
|
||||
To use GitLab as a private repository for a variety of common package managers, use the Package Registry.
|
||||
To use GitLab as a private repository for a variety of common package managers, use the package registry.
|
||||
You can build and publish
|
||||
packages, which can be consumed as dependencies in downstream projects.
|
||||
|
||||
## Supported formats
|
||||
|
||||
The Package Registry supports the following formats:
|
||||
The package registry supports the following formats:
|
||||
|
||||
| Package type | GitLab version |
|
||||
|-------------------------------------------------------------------|----------------|
|
||||
|
|
@ -55,11 +55,11 @@ guides you through the process.
|
|||
|
||||
When downloading packages as dependencies in downstream projects, many requests are made through the
|
||||
Packages API. You may therefore reach enforced user and IP rate limits. To address this issue, you
|
||||
can define specific rate limits for the Packages API. For more details, see [Package Registry Rate Limits](../settings/package_registry_rate_limits.md).
|
||||
can define specific rate limits for the Packages API. For more details, see [package registry rate limits](../settings/package_registry_rate_limits.md).
|
||||
|
||||
## Enable or disable the Package Registry
|
||||
## Enable or disable the package registry
|
||||
|
||||
The Package Registry is enabled by default. To disable it:
|
||||
The package registry is enabled by default. To disable it:
|
||||
|
||||
::Tabs
|
||||
|
||||
|
|
|
|||
|
|
@ -320,7 +320,7 @@ To select a CI/CD template for the required pipeline configuration:
|
|||
1. Select a CI/CD template from the dropdown list.
|
||||
1. Select **Save changes**.
|
||||
|
||||
## Package Registry configuration
|
||||
## Package registry configuration
|
||||
|
||||
### Maven Forwarding **(PREMIUM SELF)**
|
||||
|
||||
|
|
|
|||
|
|
@ -5,9 +5,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
|
|||
type: reference
|
||||
---
|
||||
|
||||
# Package Registry Rate Limits **(FREE SELF)**
|
||||
# Package registry rate limits **(FREE SELF)**
|
||||
|
||||
With the [GitLab Package Registry](../../user/packages/package_registry/index.md),
|
||||
With the [GitLab package registry](../../user/packages/package_registry/index.md),
|
||||
you can use GitLab as a private or public registry for a variety of common package managers. You can
|
||||
publish and share packages, which others can consume as a dependency in downstream projects through
|
||||
the [Packages API](../../api/packages.md).
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ You can change network settings to limit the rate of connections with your insta
|
|||
- [Incident management](incident_management_rate_limits.md)
|
||||
- [Issue creation](rate_limit_on_issues_creation.md)
|
||||
- [Note creation](rate_limit_on_notes_creation.md)
|
||||
- [Package Registry](package_registry_rate_limits.md)
|
||||
- [Package registry](package_registry_rate_limits.md)
|
||||
- [Pipeline creation](rate_limit_on_pipelines_creation.md)
|
||||
- [Projects API](rate_limit_on_projects_api.md)
|
||||
- [Raw endpoints](rate_limits_on_raw_endpoints.md)
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ package registry, see the [Composer package registry documentation](../../user/p
|
|||
|
||||
NOTE:
|
||||
These endpoints do not adhere to the standard API authentication methods.
|
||||
See the [Composer package registry documentation](../../user/packages/composer_repository/index.md)
|
||||
See the [Composer Package Registry documentation](../../user/packages/composer_repository/index.md)
|
||||
for details on which headers and token types are supported. Undocumented authentication methods might be removed in the future.
|
||||
|
||||
## Base repository request
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This API is used by the [npm package manager client](https://docs.npmjs.com/)
|
|||
and is not meant for manual consumption.
|
||||
|
||||
For instructions on how to upload and install npm packages from the GitLab
|
||||
package registry, see the [npm package registry documentation](../../user/packages/npm_registry/index.md).
|
||||
Package Registry, see the [npm package registry documentation](../../user/packages/npm_registry/index.md).
|
||||
|
||||
NOTE:
|
||||
These endpoints do not adhere to the standard API authentication methods.
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This API is used by the [NuGet package manager client](https://www.nuget.org/)
|
|||
and is generally not meant for manual consumption.
|
||||
|
||||
For instructions on how to upload and install NuGet packages from the GitLab
|
||||
package registry, see the [NuGet package registry documentation](../../user/packages/nuget_repository/index.md).
|
||||
Package Registry, see the [NuGet package registry documentation](../../user/packages/nuget_repository/index.md).
|
||||
|
||||
NOTE:
|
||||
These endpoints do not adhere to the standard API authentication methods.
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This API is used by the [PyPI package manager client](https://pypi.org/)
|
|||
and is generally not meant for manual consumption.
|
||||
|
||||
For instructions on how to upload and install PyPI packages from the GitLab
|
||||
package registry, see the [PyPI package registry documentation](../../user/packages/pypi_repository/index.md).
|
||||
Package Registry, see the [PyPI package registry documentation](../../user/packages/pypi_repository/index.md).
|
||||
|
||||
NOTE:
|
||||
These endpoints do not adhere to the standard API authentication methods.
|
||||
|
|
|
|||
|
|
@ -2967,8 +2967,7 @@ PUT /projects/:id/push_rule
|
|||
|
||||
> Moved to GitLab Premium in 13.9.
|
||||
|
||||
Removes a push rule from a project. This method is idempotent and can be
|
||||
called multiple times. Either the push rule is available or not.
|
||||
Removes a push rule from a project.
|
||||
|
||||
```plaintext
|
||||
DELETE /projects/:id/push_rule
|
||||
|
|
|
|||
|
|
@ -651,7 +651,7 @@ to be set, or _all_ of these values to be set:
|
|||
|
||||
::EndTabs
|
||||
|
||||
### Package Registry: Package file size limits
|
||||
### Package registry: Package file size limits
|
||||
|
||||
The package file size limits are not part of the Application settings API.
|
||||
Instead, these settings can be accessed using the [Plan limits API](plan_limits.md).
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ consistent choices, despite all goals being important, we defined the following
|
|||
Examples:
|
||||
|
||||
- a proposal improves maintainability at the cost of perceived performance: ❌ we should consider an alternative.
|
||||
- a proposal removes a feature from certain contexts, hurting coverage, and has no impact on perceived performance or maintanability: ❌ we should re-consider.
|
||||
- a proposal removes a feature from certain contexts, hurting coverage, and has no impact on perceived performance or maintainability: ❌ we should re-consider.
|
||||
- a proposal improves perceived performance but removes features from certain contexts of usage: ✅ it's valid and should be discussed with Product/UX.
|
||||
- a proposal guarantees consistent coverage and has no impact on perceived performance or maintainability: ✅ it's valid.
|
||||
|
||||
|
|
@ -72,7 +72,7 @@ compared with the pros and cons of alternatives.
|
|||
|
||||
- We will store implementation details like metrics, budgets, and development & architectural patterns here in the docs
|
||||
- We will store large bodies of research, the results of audits, etc. in the [wiki](https://gitlab.com/gitlab-com/create-stage/new-diffs/-/wikis/home) of the [New Diffs project](https://gitlab.com/gitlab-com/create-stage/new-diffs)
|
||||
- We will store audio & video recordings on the public Youtube channel in the Code Review / New Diffs playlist
|
||||
- We will store audio & video recordings on the public YouTube channel in the Code Review / New Diffs playlist
|
||||
- We will store drafts, meeting notes, and other temporary documents in public Google docs
|
||||
|
||||
### Definitions
|
||||
|
|
@ -84,7 +84,7 @@ Maintainable projects are _simple_ projects.
|
|||
Simplicity is the opposite of complexity. This uses a definition of simple and complex [described by Rich Hickey in "Simple Made Easy"](https://www.infoq.com/presentations/Simple-Made-Easy/) (Strange Loop, 2011).
|
||||
|
||||
- Maintainable code is simple (single task, single concept, separate from other things).
|
||||
- Maintainable projects expand on simple code by having simple structure (folders define classes of behaviors, e.g. you can be assured that a component directory will never initiate a network call, because that would be complecting visual display with data access)
|
||||
- Maintainable projects expand on simple code by having simple structure (folders define classes of behaviors, e.g. you can be assured that a component directory will never initiate a network call, because that would be conflating visual display with data access)
|
||||
- Maintainable applications flow out of simple organization and simple code. The old saying is a cluttered desk is representative of a cluttered mind. Rigorous discipline on simplicity will be represented in our output (the product). By being strict about working simply, we will naturally produce applications where our users can more easily reason about their behavior.
|
||||
|
||||
#### Done
|
||||
|
|
@ -94,9 +94,30 @@ GitLab has an existing [definition of done](/ee/development/contributing/merge_r
|
|||
In addition to the items in the GitLab definition of done, work on new diffs should also adhere to the following requirements:
|
||||
|
||||
- Meets or exceeds all metrics
|
||||
- Meets or exceeds our minimum accessibility metrics (these are explicitly not part of our defined priorities, since they are non-negotiable)
|
||||
- Meets or exceeds our minimum accessibility metrics (these are explicitly not part of our defined priorities, because they are non-negotiable)
|
||||
- All work is fully documented for engineers (user documentation is a requirement of the standard definition of done)
|
||||
|
||||
### Metrics
|
||||
|
||||
To measure our success, we need to set meaningful metrics. These metrics should meaningfully and positively impact the end user.
|
||||
|
||||
1. Meets or exceeds [WCAG 2.2 AA](https://www.w3.org/TR/WCAG22/).
|
||||
1. Meets or exceeds [ATAG 2.0 AA](https://www.w3.org/TR/ATAG20/).
|
||||
1. The new Diffs app loads less than or equal to 300 KiB of JavaScript (compressed / "across-the-wire")<sup>1</sup>.
|
||||
1. The new Diffs app loads less than or equal to 150 KiB of markup, images, styles, fonts, etc. (compressed / "across-the-wire")<sup>1</sup>.
|
||||
1. The new Diffs app can load and execute in total isolation from the rest of the GitLab product:
|
||||
1. "Execute" means the app can load, display data, and allows user interaction ("read-only").
|
||||
1. If a part of the application is only used in merge requests or diffs, it is considered part of the Diffs application.
|
||||
1. If a part of the application must be brought in from the rest of the product, it is not considered part of the Diffs load (as defined in metrics 3 and 4).
|
||||
1. If a part of the application must be brought in from the rest of the product, it may not block functionality of the Diffs application.
|
||||
1. If a part of the application must be brought in from the rest of the product, it must be loaded asynchronously.
|
||||
1. If a part of the application meets 5.1-5.5 _(such as: the Markdown editor is loaded asynchronously when the user would like to leave a comment on a diff)_ and its inclusion causes a budget overflow:
|
||||
- It must be added to a list of documented exceptions that we accept are out of bounds and out of our control.
|
||||
- The exceptions list should be addressed on a regular basis to determine the ongoing value of overflowing our budget.
|
||||
|
||||
---
|
||||
<sup>1</sup>: [The Performance Inequality Gap, 2023](https://infrequently.org/2022/12/performance-baseline-2023/)
|
||||
|
||||
<!--
|
||||
This section should contain enough information that the specifics of your
|
||||
change are understandable. This may include API specs (though not always
|
||||
|
|
|
|||
|
|
@ -59,12 +59,8 @@ Prerequisites:
|
|||
|
||||
## View a dashboard
|
||||
|
||||
> Kubernetes watch API integration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/422945) in GitLab 16.6 [with a flag](../../administration/feature_flags.md) named `k8s_watch_api`. Disabled by default.
|
||||
|
||||
FLAG:
|
||||
On self-managed GitLab, by default the Kubernetes watch API integration is not available.
|
||||
To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `k8s_watch_api`.
|
||||
On GitLab.com, this feature is available.
|
||||
> - Kubernetes watch API integration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/422945) in GitLab 16.6 [with a flag](../../administration/feature_flags.md) named `k8s_watch_api`. Disabled by default.
|
||||
> - Kubernetes watch API integration [enabled by default](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/136831) in GitLab 16.7.
|
||||
|
||||
View a dashboard to see the status of any connected clusters.
|
||||
If the `k8s_watch_api` feature flag is enabled, the status of your
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ The following table lists examples with step-by-step tutorials that are containe
|
|||
| GitLab Pages | See the [GitLab Pages](../../user/project/pages/index.md) documentation for a complete example of deploying a static site. |
|
||||
| End-to-end testing | [End-to-end testing with GitLab CI/CD and WebdriverIO](end_to_end_testing_webdriverio/index.md). |
|
||||
| Multi project pipeline | [Build, test deploy using multi project pipeline](https://gitlab.com/gitlab-examples/upstream-project). |
|
||||
| npm with semantic-release | [Publish npm packages to the GitLab Package Registry using semantic-release](semantic-release.md). |
|
||||
| npm with semantic-release | [Publish npm packages to the GitLab package registry using semantic-release](semantic-release.md). |
|
||||
| PHP with Laravel, Envoy | [Test and deploy Laravel applications with GitLab CI/CD and Envoy](laravel_with_gitlab_and_envoy/index.md). |
|
||||
| PHP with npm, SCP | [Running Composer and npm scripts with deployment via SCP in GitLab CI/CD](deployment/composer-npm-deploy.md). |
|
||||
| PHP with PHPUnit, `atoum` | [Testing PHP projects](php.md). |
|
||||
|
|
|
|||
|
|
@ -4,16 +4,16 @@ group: Package Registry
|
|||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
# Publish npm packages to the GitLab Package Registry using semantic-release **(FREE ALL)**
|
||||
# Publish npm packages to the GitLab package registry using semantic-release **(FREE ALL)**
|
||||
|
||||
This guide demonstrates how to automatically publish npm packages to the [GitLab Package Registry](../../user/packages/npm_registry/index.md) by using [semantic-release](https://github.com/semantic-release/semantic-release).
|
||||
This guide demonstrates how to automatically publish npm packages to the [GitLab package registry](../../user/packages/npm_registry/index.md) by using [semantic-release](https://github.com/semantic-release/semantic-release).
|
||||
|
||||
You can also view or fork the complete [example source](https://gitlab.com/gitlab-examples/semantic-release-npm).
|
||||
|
||||
## Initialize the module
|
||||
|
||||
1. Open a terminal and navigate to the project's repository.
|
||||
1. Run `npm init`. Name the module according to [the Package Registry's naming conventions](../../user/packages/npm_registry/index.md#naming-convention). For example, if the project's path is `gitlab-examples/semantic-release-npm`, name the module `@gitlab-examples/semantic-release-npm`.
|
||||
1. Run `npm init`. Name the module according to [the package registry's naming conventions](../../user/packages/npm_registry/index.md#naming-convention). For example, if the project's path is `gitlab-examples/semantic-release-npm`, name the module `@gitlab-examples/semantic-release-npm`.
|
||||
|
||||
1. Install the following npm packages:
|
||||
|
||||
|
|
@ -82,7 +82,7 @@ publish:
|
|||
|
||||
This example configures the pipeline with a single job, `publish`, which runs `semantic-release`. The semantic-release library publishes new versions of the npm package and creates new GitLab releases (if necessary).
|
||||
|
||||
The default `before_script` generates a temporary `.npmrc` that is used to authenticate to the Package Registry during the `publish` job.
|
||||
The default `before_script` generates a temporary `.npmrc` that is used to authenticate to the package registry during the `publish` job.
|
||||
|
||||
## Set up CI/CD variables
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ When a pipeline job is about to run, GitLab generates a unique token and injects
|
|||
You can use a GitLab CI/CD job token to authenticate with specific API endpoints:
|
||||
|
||||
- Packages:
|
||||
- [Package Registry](../../user/packages/package_registry/index.md#to-build-packages).
|
||||
- [Package registry](../../user/packages/package_registry/index.md#to-build-packages).
|
||||
- [Packages API](../../api/packages.md) (project-level).
|
||||
- [Container registry](../../user/packages/container_registry/build_and_push_images.md#use-gitlab-cicd)
|
||||
(the `$CI_REGISTRY_PASSWORD` is `$CI_JOB_TOKEN`).
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@ You can use Sigstore and npm, together with GitLab CI/CD, to digitally sign buil
|
|||
CLI provenance generation allows users to trust and verify that the package they are downloading and using is from you and the
|
||||
build system that built it.
|
||||
|
||||
For more information on how to publish npm packages, see [GitLab npm Package Registry](../../user/packages/npm_registry/index.md).
|
||||
For more information on how to publish npm packages, see [GitLab npm package registry](../../user/packages/npm_registry/index.md).
|
||||
|
||||
### Sigstore
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Global Search
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Advanced search development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: AI-powered
|
||||
group: Duo Chat
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# GitLab Duo Chat
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: AI-powered
|
||||
group: AI Framework
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# AI features based on 3rd-party integrations
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: AI-powered
|
||||
group: AI Framework
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Working with AI prompts
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Systems
|
||||
group: Distribution
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Application limits development
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Platforms
|
||||
group: Scalability
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# GitLab Application Service Level Indicators (SLIs)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Platforms
|
||||
group: Scalability
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Rails request SLIs (service level indicators)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Platforms
|
||||
group: Scalability
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Sidekiq execution SLIs (service level indicators)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Govern
|
||||
group: Compliance
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Audit event development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Deploy
|
||||
group: Environments
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Auto DevOps development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Systems
|
||||
group: Distribution
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Avoiding required stops
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Source Code
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Source Code - Gitaly Touch Points
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Source Code
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Create: Source Code backend
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Source Code
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Source Code REST endpoints
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Systems
|
||||
group: Distribution
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Building a package for testing
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Manage
|
||||
group: Import and Integrate
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Group migration by direct transfer
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Cloud Connector
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Cached queries guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Govern
|
||||
group: Authentication
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Cascading Settings
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Tenant Scale
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# GitLab Cells Development Guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Deploy
|
||||
group: Environments
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# ChatOps on GitLab.com
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Verify
|
||||
group: Pipeline Authoring
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Documenting the `.gitlab-ci.yml` keywords
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Verify
|
||||
group: Pipeline Execution
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Add new tables to the CI database
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Verify
|
||||
group: Pipeline Execution
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
type: index, concepts, howto
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: none
|
||||
group: Incubation Engineering
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Pipeline Wizard
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Verify
|
||||
group: Pipeline Authoring
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
type: index, howto
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Verify
|
||||
group: Pipeline Authoring
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
type: index, concepts, howto
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Cloud Connector
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Cloud Connector MVC: Code Suggestions for Self-Managed/GitLab Dedicated
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Code Review
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Code intelligence development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Source Code
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Code Owners development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Create
|
||||
group: Code Creation
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Code Suggestions development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Science
|
||||
group: ModelOps
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
- [Model Registry](model_registry/index.md)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Science
|
||||
group: ModelOps
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Model Registry
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Add a foreign key constraint to an existing column
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Adding Database Indexes
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Avoiding downtime in migrations
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# CI mirrored tables
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# ClickHouse within GitLab
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Store GitLab activity data in ClickHouse
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Introduction to ClickHouse use and table design
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Merge request analytics with ClickHouse
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Optimizing query execution
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Tiered Storages in ClickHouse
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Client-side connection-pool
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Constraints naming conventions
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Creating enums
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Troubleshooting and debugging the database
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database Dictionary
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database Lab and Postgres.ai
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database migration pipeline
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database query comments with Marginalia
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database Reviewer Guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Importing a database dump into a staging environment
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# db:check-migrations job
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Delete existing migrations
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Efficient `IN` operator queries
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Plan
|
||||
group: Project Management
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
# Filtering by label
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Foreign keys and associations
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Hash Indexes
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database development guidelines
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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`
|
||||
in Rails 6, which operates at the row level (that is, using `Hash`es), GitLab has added a set
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Iterating tables in batches
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Keyset pagination
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Best practices for data layout and access patterns
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
stage: Data Stores
|
||||
group: Database
|
||||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
|
||||
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.
|
||||
---
|
||||
|
||||
# Database load balancing
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue