diff --git a/GITLAB_KAS_VERSION b/GITLAB_KAS_VERSION index 9095e741ed5..91bd899a7af 100644 --- a/GITLAB_KAS_VERSION +++ b/GITLAB_KAS_VERSION @@ -1 +1 @@ -3f4f571017c2c86de35d1d7c4c1a7dded9a42e82 +1ae70272d95c4c8128d8e8eb7c3dd0569f9980e4 diff --git a/argo_translation.yml b/argo_translation.yml index 7d566be658b..6439818c6ea 100644 --- a/argo_translation.yml +++ b/argo_translation.yml @@ -10,3 +10,6 @@ components: target: 'doc-locale/{{language}}/' ignored_paths: - 'doc/.*/**' + - 'doc/architecture/**' + - 'doc/drawers/**' + - 'doc/development/**' diff --git a/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_group_id.yml b/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_group_id.yml index d760e732abc..6b136f7af42 100644 --- a/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_group_id.yml +++ b/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_group_id.yml @@ -5,4 +5,4 @@ feature_category: importers introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175723 milestone: '17.8' queued_migration_version: 20241213150054 -finalized_by: # version of the migration that finalized this BBM +finalized_by: 20250529030137 diff --git a/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_project_id.yml b/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_project_id.yml index 37dd3af6ef1..c18dca896ee 100644 --- a/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_project_id.yml +++ b/db/docs/batched_background_migrations/backfill_bulk_import_export_uploads_project_id.yml @@ -5,4 +5,4 @@ feature_category: importers introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/175723 milestone: '17.8' queued_migration_version: 20241213150049 -finalized_by: # version of the migration that finalized this BBM +finalized_by: 20250529030008 diff --git a/db/docs/batched_background_migrations/backfill_design_management_designs_versions_namespace_id.yml b/db/docs/batched_background_migrations/backfill_design_management_designs_versions_namespace_id.yml index 5abeaaace53..e34d21ab305 100644 --- a/db/docs/batched_background_migrations/backfill_design_management_designs_versions_namespace_id.yml +++ b/db/docs/batched_background_migrations/backfill_design_management_designs_versions_namespace_id.yml @@ -5,4 +5,4 @@ feature_category: design_management introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/180220 milestone: '17.9' queued_migration_version: 20250204151108 -finalized_by: # version of the migration that finalized this BBM +finalized_by: 20250529030200 diff --git a/db/docs/batched_background_migrations/backfill_project_relation_export_uploads_project_id.yml b/db/docs/batched_background_migrations/backfill_project_relation_export_uploads_project_id.yml index bc0e956571e..87d9dbb2112 100644 --- a/db/docs/batched_background_migrations/backfill_project_relation_export_uploads_project_id.yml +++ b/db/docs/batched_background_migrations/backfill_project_relation_export_uploads_project_id.yml @@ -5,4 +5,4 @@ feature_category: importers introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182116 milestone: '17.10' queued_migration_version: 20250220130531 -finalized_by: # version of the migration that finalized this BBM +finalized_by: 20250529030226 diff --git a/db/post_migrate/20250529030008_finalize_backfill_bulk_import_export_uploads_project_id.rb b/db/post_migrate/20250529030008_finalize_backfill_bulk_import_export_uploads_project_id.rb new file mode 100644 index 00000000000..1984c9ecf7e --- /dev/null +++ b/db/post_migrate/20250529030008_finalize_backfill_bulk_import_export_uploads_project_id.rb @@ -0,0 +1,26 @@ +# frozen_string_literal: true + +class FinalizeBackfillBulkImportExportUploadsProjectId < Gitlab::Database::Migration[2.3] + disable_ddl_transaction! + restrict_gitlab_migration gitlab_schema: :gitlab_main + milestone '18.1' + + def up + ensure_batched_background_migration_is_finished( + job_class_name: 'BackfillBulkImportExportUploadsProjectId', + table_name: :bulk_import_export_uploads, + column_name: :id, + job_arguments: [ + :project_id, + :bulk_import_exports, + :project_id, + :export_id + ], + finalize: true + ) + end + + def down + # no-op + end +end diff --git a/db/post_migrate/20250529030137_finalize_backfill_bulk_import_export_uploads_group_id.rb b/db/post_migrate/20250529030137_finalize_backfill_bulk_import_export_uploads_group_id.rb new file mode 100644 index 00000000000..4bf35bd9eed --- /dev/null +++ b/db/post_migrate/20250529030137_finalize_backfill_bulk_import_export_uploads_group_id.rb @@ -0,0 +1,26 @@ +# frozen_string_literal: true + +class FinalizeBackfillBulkImportExportUploadsGroupId < Gitlab::Database::Migration[2.3] + disable_ddl_transaction! + restrict_gitlab_migration gitlab_schema: :gitlab_main + milestone '18.1' + + def up + ensure_batched_background_migration_is_finished( + job_class_name: 'BackfillBulkImportExportUploadsGroupId', + table_name: :bulk_import_export_uploads, + column_name: :id, + job_arguments: [ + :group_id, + :bulk_import_exports, + :group_id, + :export_id + ], + finalize: true + ) + end + + def down + # no-op + end +end diff --git a/db/post_migrate/20250529030200_finalize_design_management_designs_versions_namespace_id.rb b/db/post_migrate/20250529030200_finalize_design_management_designs_versions_namespace_id.rb new file mode 100644 index 00000000000..f70950c7e21 --- /dev/null +++ b/db/post_migrate/20250529030200_finalize_design_management_designs_versions_namespace_id.rb @@ -0,0 +1,26 @@ +# frozen_string_literal: true + +class FinalizeDesignManagementDesignsVersionsNamespaceId < Gitlab::Database::Migration[2.3] + disable_ddl_transaction! + restrict_gitlab_migration gitlab_schema: :gitlab_main + milestone '18.1' + + def up + ensure_batched_background_migration_is_finished( + job_class_name: 'BackfillDesignManagementDesignsVersionsNamespaceId', + table_name: :design_management_designs_versions, + column_name: :id, + job_arguments: [ + :namespace_id, + :design_management_designs, + :namespace_id, + :design_id + ], + finalize: true + ) + end + + def down + # no-op + end +end diff --git a/db/post_migrate/20250529030226_finalize_queue_backfill_project_relation_export_uploads_project_id.rb b/db/post_migrate/20250529030226_finalize_queue_backfill_project_relation_export_uploads_project_id.rb new file mode 100644 index 00000000000..3f80edc4f25 --- /dev/null +++ b/db/post_migrate/20250529030226_finalize_queue_backfill_project_relation_export_uploads_project_id.rb @@ -0,0 +1,26 @@ +# frozen_string_literal: true + +class FinalizeQueueBackfillProjectRelationExportUploadsProjectId < Gitlab::Database::Migration[2.3] + disable_ddl_transaction! + restrict_gitlab_migration gitlab_schema: :gitlab_main + milestone '18.1' + + def up + ensure_batched_background_migration_is_finished( + job_class_name: 'BackfillProjectRelationExportUploadsProjectId', + table_name: :project_relation_export_uploads, + column_name: :id, + job_arguments: [ + :project_id, + :project_relation_exports, + :project_id, + :project_relation_export_id + ], + finalize: true + ) + end + + def down + # no-op + end +end diff --git a/db/schema_migrations/20250529030008 b/db/schema_migrations/20250529030008 new file mode 100644 index 00000000000..26c261bf613 --- /dev/null +++ b/db/schema_migrations/20250529030008 @@ -0,0 +1 @@ +2f23ab0a1cd16bbe3d2aacc9e4d0914381110389f0156a3057d249c2dd6beff4 \ No newline at end of file diff --git a/db/schema_migrations/20250529030137 b/db/schema_migrations/20250529030137 new file mode 100644 index 00000000000..06f8c6c5770 --- /dev/null +++ b/db/schema_migrations/20250529030137 @@ -0,0 +1 @@ +c608596bb4a32a0405427db248ac740561a3e34e5ae91b9f947ba9242340f9b4 \ No newline at end of file diff --git a/db/schema_migrations/20250529030200 b/db/schema_migrations/20250529030200 new file mode 100644 index 00000000000..d640333e14d --- /dev/null +++ b/db/schema_migrations/20250529030200 @@ -0,0 +1 @@ +6d9d95480c3f4c461473fc10a90524f507a5af0c1e0b77bd730423064e269100 \ No newline at end of file diff --git a/db/schema_migrations/20250529030226 b/db/schema_migrations/20250529030226 new file mode 100644 index 00000000000..ab04fc5193b --- /dev/null +++ b/db/schema_migrations/20250529030226 @@ -0,0 +1 @@ +8015a31907d1cf8a306599e05b74cbf26b5190a0f46d565d1eb095ab234ec486 \ No newline at end of file diff --git a/doc-locale/ja-jp/development/_index.md b/doc-locale/ja-jp/development/_index.md new file mode 100644 index 00000000000..80dbb79de18 --- /dev/null +++ b/doc-locale/ja-jp/development/_index.md @@ -0,0 +1,7 @@ +--- +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. +description: 'Development Guidelines: learn how to contribute to GitLab.' +title: Contribute to development +--- diff --git a/doc-locale/ja-jp/development/activitypub/_index.md b/doc-locale/ja-jp/development/activitypub/_index.md new file mode 100644 index 00000000000..56ca2223a54 --- /dev/null +++ b/doc-locale/ja-jp/development/activitypub/_index.md @@ -0,0 +1,6 @@ +--- +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 +title: ActivityPub +--- diff --git a/doc-locale/ja-jp/development/activitypub/actors/_index.md b/doc-locale/ja-jp/development/activitypub/actors/_index.md new file mode 100644 index 00000000000..b295758ea08 --- /dev/null +++ b/doc-locale/ja-jp/development/activitypub/actors/_index.md @@ -0,0 +1,6 @@ +--- +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 +title: Implement an ActivityPub actor +--- diff --git a/doc-locale/ja-jp/development/activitypub/actors/releases.md b/doc-locale/ja-jp/development/activitypub/actors/releases.md new file mode 100644 index 00000000000..1bbb6a3ba51 --- /dev/null +++ b/doc-locale/ja-jp/development/activitypub/actors/releases.md @@ -0,0 +1,6 @@ +--- +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 +title: Activities for following releases actor +--- diff --git a/doc-locale/ja-jp/development/adding_service_component.md b/doc-locale/ja-jp/development/adding_service_component.md new file mode 100644 index 00000000000..9dc015a7732 --- /dev/null +++ b/doc-locale/ja-jp/development/adding_service_component.md @@ -0,0 +1,6 @@ +--- +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. +title: Adding a new Service Component to GitLab +--- diff --git a/doc-locale/ja-jp/development/advanced_search.md b/doc-locale/ja-jp/development/advanced_search.md new file mode 100644 index 00000000000..707b095b1d2 --- /dev/null +++ b/doc-locale/ja-jp/development/advanced_search.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Global Search +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +title: Advanced search development guidelines +--- diff --git a/doc-locale/ja-jp/development/advanced_search/tips.md b/doc-locale/ja-jp/development/advanced_search/tips.md new file mode 100644 index 00000000000..0a240b9d203 --- /dev/null +++ b/doc-locale/ja-jp/development/advanced_search/tips.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Global Search +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. +title: Advanced search development tips +--- diff --git a/doc-locale/ja-jp/development/ai_architecture.md b/doc-locale/ja-jp/development/ai_architecture.md new file mode 100644 index 00000000000..db5d19c7ef9 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_architecture.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: AI Architecture +--- diff --git a/doc-locale/ja-jp/development/ai_features/_index.md b/doc-locale/ja-jp/development/ai_features/_index.md new file mode 100644 index 00000000000..2a86e6019f6 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/_index.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: AI features based on 3rd-party integrations +--- diff --git a/doc-locale/ja-jp/development/ai_features/actions.md b/doc-locale/ja-jp/development/ai_features/actions.md new file mode 100644 index 00000000000..1ad1a56e77f --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/actions.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: AI actions +--- diff --git a/doc-locale/ja-jp/development/ai_features/ai_development_license.md b/doc-locale/ja-jp/development/ai_features/ai_development_license.md new file mode 100644 index 00000000000..7527666bf57 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/ai_development_license.md @@ -0,0 +1,7 @@ +--- +stage: AI-powered +group: AI Framework +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: Documentation about GitLab Duo licensing options for local development +title: GitLab Duo licensing for local development +--- diff --git a/doc-locale/ja-jp/development/ai_features/ai_feature_development_playbook.md b/doc-locale/ja-jp/development/ai_features/ai_feature_development_playbook.md new file mode 100644 index 00000000000..55cc44c62d2 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/ai_feature_development_playbook.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: AI feature development playbook +--- diff --git a/doc-locale/ja-jp/development/ai_features/amazon_q_integration.md b/doc-locale/ja-jp/development/ai_features/amazon_q_integration.md new file mode 100644 index 00000000000..304df38c9d2 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/amazon_q_integration.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: Custom Models +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. +title: Amazon Q integration for testing and evaluation +--- diff --git a/doc-locale/ja-jp/development/ai_features/code_suggestions.md b/doc-locale/ja-jp/development/ai_features/code_suggestions.md new file mode 100644 index 00000000000..f0f78e2b8cc --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/code_suggestions.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Creation +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: Code Suggestions documentation for developers interested in contributing features or bugfixes. +title: Code Suggestions development guidelines +--- diff --git a/doc-locale/ja-jp/development/ai_features/composite_identity.md b/doc-locale/ja-jp/development/ai_features/composite_identity.md new file mode 100644 index 00000000000..57da978ccb6 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/composite_identity.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: Composite Identity +--- diff --git a/doc-locale/ja-jp/development/ai_features/duo_chat.md b/doc-locale/ja-jp/development/ai_features/duo_chat.md new file mode 100644 index 00000000000..7889e0b4ac4 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/duo_chat.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: Duo Chat +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. +title: GitLab Duo Chat +--- diff --git a/doc-locale/ja-jp/development/ai_features/embeddings.md b/doc-locale/ja-jp/development/ai_features/embeddings.md new file mode 100644 index 00000000000..ec850141e41 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/embeddings.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Global Search +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. +title: Embeddings +--- diff --git a/doc-locale/ja-jp/development/ai_features/evaluation_runner/_index.md b/doc-locale/ja-jp/development/ai_features/evaluation_runner/_index.md new file mode 100644 index 00000000000..9ac5fc5c5d8 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/evaluation_runner/_index.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: Evaluation runner +--- diff --git a/doc-locale/ja-jp/development/ai_features/glossary.md b/doc-locale/ja-jp/development/ai_features/glossary.md new file mode 100644 index 00000000000..bbb4d206815 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/glossary.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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 +title: GitLab Duo Glossary +--- diff --git a/doc-locale/ja-jp/development/ai_features/local_models.md b/doc-locale/ja-jp/development/ai_features/local_models.md new file mode 100644 index 00000000000..e9a44474718 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/local_models.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: Custom Models +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 +title: Serve Large Language Models APIs Locally +--- diff --git a/doc-locale/ja-jp/development/ai_features/logged_events.md b/doc-locale/ja-jp/development/ai_features/logged_events.md new file mode 100644 index 00000000000..5504c43765b --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/logged_events.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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 +title: Logged events +--- diff --git a/doc-locale/ja-jp/development/ai_features/logging.md b/doc-locale/ja-jp/development/ai_features/logging.md new file mode 100644 index 00000000000..41ace50deb5 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/logging.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: LLM logging +--- diff --git a/doc-locale/ja-jp/development/ai_features/model_migration.md b/doc-locale/ja-jp/development/ai_features/model_migration.md new file mode 100644 index 00000000000..60bf9fc2612 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/model_migration.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: Model Migration Process +--- diff --git a/doc-locale/ja-jp/development/ai_features/testing_and_validation.md b/doc-locale/ja-jp/development/ai_features/testing_and_validation.md new file mode 100644 index 00000000000..c690020b307 --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/testing_and_validation.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: Testing and Validation +--- diff --git a/doc-locale/ja-jp/development/ai_features/vertex_model_enablement_process.md b/doc-locale/ja-jp/development/ai_features/vertex_model_enablement_process.md new file mode 100644 index 00000000000..74033173edf --- /dev/null +++ b/doc-locale/ja-jp/development/ai_features/vertex_model_enablement_process.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: AI Framework +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. +title: Vertex AI Model Enablement Process +--- diff --git a/doc-locale/ja-jp/development/api_graphql_styleguide.md b/doc-locale/ja-jp/development/api_graphql_styleguide.md new file mode 100644 index 00000000000..e49b5bd5e81 --- /dev/null +++ b/doc-locale/ja-jp/development/api_graphql_styleguide.md @@ -0,0 +1,6 @@ +--- +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. +title: Backend GraphQL API guide +--- diff --git a/doc-locale/ja-jp/development/api_styleguide.md b/doc-locale/ja-jp/development/api_styleguide.md new file mode 100644 index 00000000000..ff59382325c --- /dev/null +++ b/doc-locale/ja-jp/development/api_styleguide.md @@ -0,0 +1,6 @@ +--- +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. +title: API style guide +--- diff --git a/doc-locale/ja-jp/development/application_limits.md b/doc-locale/ja-jp/development/application_limits.md new file mode 100644 index 00000000000..b7e02d99dfa --- /dev/null +++ b/doc-locale/ja-jp/development/application_limits.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Distribution +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. +title: Application limits development +--- diff --git a/doc-locale/ja-jp/development/application_secrets.md b/doc-locale/ja-jp/development/application_secrets.md new file mode 100644 index 00000000000..ed0d0e9171f --- /dev/null +++ b/doc-locale/ja-jp/development/application_secrets.md @@ -0,0 +1,6 @@ +--- +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. +title: Application secrets +--- diff --git a/doc-locale/ja-jp/development/application_settings.md b/doc-locale/ja-jp/development/application_settings.md new file mode 100644 index 00000000000..ccfe62d2455 --- /dev/null +++ b/doc-locale/ja-jp/development/application_settings.md @@ -0,0 +1,6 @@ +--- +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. +title: Application settings development +--- diff --git a/doc-locale/ja-jp/development/application_slis/_index.md b/doc-locale/ja-jp/development/application_slis/_index.md new file mode 100644 index 00000000000..7dc1d8599c9 --- /dev/null +++ b/doc-locale/ja-jp/development/application_slis/_index.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: GitLab Application Service Level Indicators (SLIs) +--- diff --git a/doc-locale/ja-jp/development/application_slis/rails_request.md b/doc-locale/ja-jp/development/application_slis/rails_request.md new file mode 100644 index 00000000000..910b52b2b5b --- /dev/null +++ b/doc-locale/ja-jp/development/application_slis/rails_request.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Rails request SLIs (service level indicators) +--- diff --git a/doc-locale/ja-jp/development/application_slis/sidekiq_execution.md b/doc-locale/ja-jp/development/application_slis/sidekiq_execution.md new file mode 100644 index 00000000000..d6d9a00093c --- /dev/null +++ b/doc-locale/ja-jp/development/application_slis/sidekiq_execution.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Sidekiq execution SLIs (service level indicators) +--- diff --git a/doc-locale/ja-jp/development/architecture.md b/doc-locale/ja-jp/development/architecture.md index fec16250b1b..1100a105106 100644 --- a/doc-locale/ja-jp/development/architecture.md +++ b/doc-locale/ja-jp/development/architecture.md @@ -2,1095 +2,5 @@ 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. -title: GitLabアーキテクチャの概要 +title: GitLab architecture overview --- - -## ソフトウェアデリバリー - -GitLabのソフトウェアディストリビューションには2種類あります。 - -- オープンソースの[Community Edition](https://gitlab.com/gitlab-org/gitlab-foss/)（CE）。 -- オープンコアの[Enterprise Edition](https://gitlab.com/gitlab-org/gitlab/)（EE）。 - -EEリポジトリはアーカイブされました。GitLabは現在、[単一のコードベース](https://about.gitlab.com/blog/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/)で運用しています。 - -GitLabは[さまざまなサブスクリプション](https://about.gitlab.com/pricing/)で利用できます。 - -GitLabの新しいバージョンは安定したブランチからリリースしていて、最先端の開発には`main`ブランチを使用します。 - -詳細については、[GitLabリリースプロセス](https://handbook.gitlab.com/handbook/engineering/releases/)を参照してください。 - -どちらのディストリビューションにも追加のコンポーネントが必要です。追加のコンポーネントについては[コンポーネントの詳細](#components)セクションで説明していますが、すべて独自のリポジトリを備えています。各依存コンポーネントの新バージョンは通常はタグですが、GitLabコードベースの`main`ブランチを使用すると、そのコンポーネントの最新の安定バージョンを入手できます。新バージョンは通常、GitLabのリリースとほぼ同時にリリースされますが、重大と見なされる非公式のセキュリティアップデートは例外です。 - -## コンポーネント - -GitLabの一般的なインストールはGNU/Linux上で行いますが、Kubernetesプラットフォームを使用するデプロイも増えています。既知の最大のGitLabインスタンスはGitLab.com上にあり、[公式GitLab Helmチャート](https://docs.gitlab.com/charts/)と[公式Linuxパッケージ](https://about.gitlab.com/install/)を使用してデプロイしています。 - -一般的なインストールでは、WebサーバーとしてNGINXまたはApacheを使用し、[GitLab Workhorse](https://gitlab.com/gitlab-org/gitlab/tree/master/workhorse)をプロキシとして経由して[Puma](https://puma.io)アプリケーションサーバーにアクセスします。GitLabは、Pumaアプリケーションサーバーを使用してWebページと[GitLab API](../api/rest/_index.md)を提供します。Sidekiqをジョブキューとして使用し、同様にRedisをジョブ情報、メタデータ、受信ジョブの非永続化データベースバックエンドとして使用します。 - -デフォルトでは、PumaとWorkhorse間の通信はUnixドメインソケット経由ですが、TCP経由でリクエストの転送もサポートしています。Workhorseは`gitlab/public`ディレクトリにアクセスし、Pumaアプリケーションサーバーをバイパスして、静的ページ、アバター画像や添付ファイルなどのアップロード、プリコンパイル済みの資産を提供します。 - -GitLabアプリケーションは、永続化データベース情報（ユーザー、権限、イシュー、その他のメタデータなど）にPostgreSQLを使用します。GitLabは、[設定ファイルの`repositories:`セクション](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example)で定義した場所にGitのベアリポジトリを格納します。デフォルトのブランチとフック情報も、ベアリポジトリで保持します。 - -HTTP/HTTPSでリポジトリを機能させる場合、GitLabはGitLab APIを使用して認証とアクセスを解決し、Gitオブジェクトを提供します。 - -アドオンコンポーネントのGitLab Shellは、SSHでリポジトリを提供します。[設定ファイルの`GitLab Shell`セクション](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example)で定義した場所でSSHキーを管理します。その場所にあるファイルは、手動で編集しないでください。GitLab Shellは、Gitalyを介してベアリポジトリにアクセスしてGitオブジェクトを提供し、Redisと通信してジョブをGitLabで処理するためにSidekiqに送信します。GitLab ShellはGitLab APIにクエリを発行して、認証とアクセスを判断します。 - -Gitalyは、GitLab ShellとGitLab WebアプリからGitオペレーションを実行し、GitLab WebアプリにAPIを提供して、Gitから属性（タイトル、ブランチ、タグ、その他のメタデータなど）を取得し、blob（差分、コミット、ファイルなど）を取得します。 - -[GitLab.comの本番環境のアーキテクチャ](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/)にも興味があるかもしれません。 - -## 既存のコンポーネントに適応し新しいコンポーネントを導入する - -従来のLinuxマシンにインストールした場合、Kubernetesなどのコンテナ化したプラットフォームと比較して、アプリケーションの動作には根本的な違いがあります。 - -[公式のインストール方法](https://about.gitlab.com/install/)と比較した場合の顕著な違いを以下に挙げます。 - -- 公式のLinuxパッケージは、異なるサービスで同じファイルシステム上のファイルにアクセスできます。[共有ファイル](shared_files.md)は、Kubernetesプラットフォームで実行しているアプリケーションのオプションではありません。 -- 公式のLinuxパッケージでは、デフォルトで共有設定とネットワークにアクセスできるサービスがあります。Kubernetesで実行されているサービスではそうではなく、サービスを完全に分離して実行したり、特定のポート経由でのみアクセス可能だったりする場合があります。 - -つまり、新機能を設計して新コンポーネントを追加するときは、サービス間の共有状態を慎重に検討する必要があります。同じファイルにアクセスする必要があるサービスは、適切なAPIを通じて情報を交換できるようにする必要があります。可能であれば、これはファイルを介して行うべきではありません。 - -APIファーストの理念を念頭に置いて作成したコンポーネントは両方の方式と互換性があるため、新機能と新サービスは、必ずKubernetesとの互換性を**第一に**考慮して作成する必要があります。 - -これを確保する最も簡単な方法は、[公式のGitLab Helmチャート](https://docs.gitlab.com/charts/)に機能やサービスのサポートを追加するか、[ディストリビューションチーム](https://handbook.gitlab.com/handbook/engineering/infrastructure/core-platform/systems/distribution/#how-to-work-with-distribution)に連絡することです。 - -詳細については、[新しいサービスコンポーネントを追加するプロセス](adding_service_component.md)を参照してください。 - -### コンポーネントの概要（簡略版） - -これはGitLabアーキテクチャを理解するための、簡略化したアーキテクチャ図です。 - -完全なアーキテクチャ図は、以下の[コンポーネント図](#component-diagram)にあります。 - -```mermaid -%%{init: {"flowchart": { "useMaxWidth": false } }}%% -graph TB - %% Component declarations and formatting - HTTP((HTTP/HTTPS)) - SSH((SSH)) - GitLabPages(GitLab Pages) - GitLabWorkhorse(GitLab Workhorse) - GitLabShell(GitLab Shell) - Gitaly(Gitaly) - Puma("Puma (Gitlab Rails)") - Sidekiq("Sidekiq (GitLab Rails)") - PostgreSQL(PostgreSQL) - Redis(Redis) - - HTTP -- TCP 80,443 --> NGINX - SSH -- TCP 22 --> GitLabShell - - NGINX -- TCP 8090 --> GitLabPages - NGINX --> GitLabWorkhorse - - GitLabShell --> Gitaly - GitLabShell --> GitLabWorkhorse - - GitLabWorkhorse --> Gitaly - GitLabWorkhorse --> Puma - GitLabWorkhorse --> Redis - - Sidekiq --> PostgreSQL - Sidekiq --> Redis - - Puma --> PostgreSQL - Puma --> Redis - Puma --> Gitaly - - Gitaly --> GitLabWorkhorse -``` - -特に指定しない限り、すべての接続でUnixソケットを使用します。 - -### コンポーネント図 - -```mermaid -%%{init: {"flowchart": { "useMaxWidth": false } }}%% -graph LR - %% Anchor items in the appropriate subgraph. - %% Link them where the destination* is. - - subgraph Clients - Browser((Browser)) - Git((Git)) - end - - %% External Components / Applications - Geo{{GitLab Geo}} -- TCP 80, 443 --> HTTP - Geo -- TCP 22 --> SSH - Geo -- TCP 5432 --> PostgreSQL - Runner{{GitLab Runner}} -- TCP 443 --> HTTP - K8sAgent{{GitLab agent}} -- TCP 443 --> HTTP - - %% GitLab Application Suite - subgraph GitLab - subgraph Ingress - HTTP[[HTTP/HTTPS]] - SSH[[SSH]] - NGINX[NGINX] - GitLabShell[GitLab Shell] - - %% inbound/internal - Browser -- TCP 80,443 --> HTTP - Git -- TCP 80,443 --> HTTP - Git -- TCP 22 --> SSH - HTTP -- TCP 80, 443 --> NGINX - SSH -- TCP 22 --> GitLabShell - end - - subgraph GitLab Services - %% inbound from NGINX - NGINX --> GitLabWorkhorse - NGINX -- TCP 8090 --> GitLabPages - NGINX -- TCP 8150 --> GitLabKas - NGINX --> Registry - %% inbound from GitLabShell - GitLabShell --> GitLabWorkhorse - - %% services - Puma["Puma (GitLab Rails)"] - Puma <--> Registry - GitLabWorkhorse[GitLab Workhorse] <--> Puma - GitLabKas[GitLab agent server] --> GitLabWorkhorse - GitLabPages[GitLab Pages] --> GitLabWorkhorse - Mailroom - Sidekiq - end - - subgraph Integrated Services - %% Mattermost - Mattermost - Mattermost ---> GitLabWorkhorse - NGINX --> Mattermost - - %% Grafana - Grafana - NGINX --> Grafana - end - - subgraph Metadata - %% PostgreSQL - PostgreSQL - PostgreSQL --> Consul - - %% Consul and inbound - Consul - Puma ---> Consul - Sidekiq ---> Consul - Migrations --> PostgreSQL - - %% PgBouncer and inbound - PgBouncer - PgBouncer --> Consul - PgBouncer --> PostgreSQL - Sidekiq --> PgBouncer - Puma --> PgBouncer - end - - subgraph State - %% Redis and inbound - Redis - Puma --> Redis - Sidekiq --> Redis - GitLabWorkhorse --> Redis - Mailroom --> Redis - GitLabKas --> Redis - - %% Sentinel and inbound - Sentinel <--> Redis - Puma --> Sentinel - Sidekiq --> Sentinel - GitLabWorkhorse --> Sentinel - Mailroom --> Sentinel - GitLabKas --> Sentinel - end - - subgraph Git Repositories - %% Gitaly / Praefect - Praefect --> Gitaly - GitLabKas --> Praefect - GitLabShell --> Praefect - GitLabWorkhorse --> Praefect - Puma --> Praefect - Sidekiq --> Praefect - Praefect <--> PraefectPGSQL[PostgreSQL] - %% Gitaly makes API calls - %% Ordered here to ensure placement. - Gitaly --> GitLabWorkhorse - end - - subgraph Storage - %% ObjectStorage and inbound traffic - ObjectStorage["Object storage"] - Puma -- TCP 443 --> ObjectStorage - Sidekiq -- TCP 443 --> ObjectStorage - GitLabWorkhorse -- TCP 443 --> ObjectStorage - Registry -- TCP 443 --> ObjectStorage - GitLabPages -- TCP 443 --> ObjectStorage - %% Gitaly can perform repository backups to object storage. - Gitaly --> ObjectStorage - end - - subgraph Monitoring - %% Prometheus - Grafana -- TCP 9090 --> Prometheus[Prometheus] - Prometheus -- TCP 80, 443 --> Puma - RedisExporter[Redis Exporter] --> Redis - Prometheus -- TCP 9121 --> RedisExporter - PostgreSQLExporter[PostgreSQL Exporter] --> PostgreSQL - PgBouncerExporter[PgBouncer Exporter] --> PgBouncer - Prometheus -- TCP 9187 --> PostgreSQLExporter - Prometheus -- TCP 9100 --> NodeExporter[Node Exporter] - Prometheus -- TCP 9168 --> GitLabExporter[GitLab Exporter] - Prometheus -- TCP 9127 --> PgBouncerExporter - Prometheus --> Alertmanager - GitLabExporter --> PostgreSQL - GitLabExporter --> GitLabShell - GitLabExporter --> Sidekiq - - %% Alertmanager - Alertmanager -- TCP 25 --> SMTP - end - %% end subgraph GitLab - end - - subgraph External - subgraph External Services - SMTP[SMTP Gateway] - LDAP - - %% Outbound SMTP - Sidekiq -- TCP 25 --> SMTP - Puma -- TCP 25 --> SMTP - Mailroom -- TCP 25 --> SMTP - - %% Outbound LDAP - Puma -- TCP 369 --> LDAP - Sidekiq -- TCP 369 --> LDAP - - %% Elasticsearch - Elasticsearch - Puma -- TCP 9200 --> Elasticsearch - Sidekiq -- TCP 9200 --> Elasticsearch - Elasticsearch --> Praefect - - %% Zoekt - Zoekt --> Praefect - end - subgraph External Monitoring - %% Sentry - Sidekiq -- TCP 80, 443 --> Sentry - Puma -- TCP 80, 443 --> Sentry - - %% Jaeger - Jaeger - Sidekiq -- UDP 6831 --> Jaeger - Puma -- UDP 6831 --> Jaeger - Gitaly -- UDP 6831 --> Jaeger - GitLabShell -- UDP 6831 --> Jaeger - GitLabWorkhorse -- UDP 6831 --> Jaeger - end - %% end subgraph External - end - -click Alertmanager "#alertmanager" -click Praefect "#praefect" -click Geo "#gitlab-geo" -click NGINX "#nginx" -click Runner "#gitlab-runner" -click Registry "#registry" -click ObjectStorage "#minio" -click Mattermost "#mattermost" -click Gitaly "#gitaly" -click Jaeger "#jaeger" -click GitLabWorkhorse "#gitlab-workhorse" -click LDAP "#ldap-authentication" -click Puma "#puma" -click GitLabShell "#gitlab-shell" -click SSH "#ssh-request-22" -click Sidekiq "#sidekiq" -click Sentry "#sentry" -click GitLabExporter "#gitlab-exporter" -click Elasticsearch "#elasticsearch" -click Migrations "#database-migrations" -click PostgreSQL "#postgresql" -click Consul "#consul" -click PgBouncer "#pgbouncer" -click PgBouncerExporter "#pgbouncer-exporter" -click RedisExporter "#redis-exporter" -click Redis "#redis" -click Prometheus "#prometheus" -click Grafana "#grafana" -click GitLabPages "#gitlab-pages" -click PostgreSQLExporter "#postgresql-exporter" -click SMTP "#outbound-email" -click NodeExporter "#node-exporter" -``` - -### コンポーネントの凡例 - -- ✅ - デフォルトでインストール -- ⚙ - 追加の設定が必要 -- ⤓ - 手動インストールが必要 -- ❌ - サポートされていないか、利用可能な指示がない -- N/A - 該当なし - -コンポーネントのステータスは、各コンポーネントの設定ドキュメントにリンクしています。 - -### コンポーネントリスト - -| コンポーネント | 説明 | [オムニバスGitLab](https://docs.gitlab.com/omnibus/) | [GitLab Environment Toolkit（GET）](https://gitlab.com/gitlab-org/gitlab-environment-toolkit) | [GitLabチャート](https://docs.gitlab.com/charts/) | [minikube Minimal](https://docs.gitlab.com/charts/development/minikube/#deploying-gitlab-with-minimal-settings) | [GitLab.com](https://gitlab.com) | [ソース](../install/installation.md) | [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit) | [CE/EE](https://about.gitlab.com/install/ce-or-ee/) | -|-------------------------------------------------------|----------------------------------------------------------------------|:--------------:|:--------------:|:------------:|:----------------:|:----------:|:------:|:---:|:-------:| -| [証明書管理](#certificate-management) | TLS 設定、Let's Encrypt | ✅ | ✅ | ✅ | ⚙ | ✅ | ⚙ | ⚙ | CEとEE | -| [Consul](#consul) | データベースノードの調査、フェイルオーバー | ⚙ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | EEのみ | -| [データベースの移行](#database-migrations) | データベースの移行 | ✅ | ✅ | ✅ | ✅ | ✅ | ⚙ | ✅ | CEとEE | -| [Elasticsearch](#elasticsearch) | GitLab内の検索を改善 | ⤓ | ⚙ | ⤓ | ⤓ | ✅ | ⤓ | ⚙ | EEのみ | -| [Gitaly](#gitaly) | GitLabが行うすべてのGit呼び出しを処理するGit RPCサービス | ✅ | ✅ | ✅ | ✅ | ✅ | ⚙ | ✅ | CEとEE | -| [GitLab Exporter](#gitlab-exporter) | さまざまなGitLabメトリクスを生成 | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | CEとEE | -| [GitLab Geo](#gitlab-geo) | 地理的に分散したGitLabサイト | ⚙ | ⚙ | ❌ | ❌ | ✅ | ❌ | ⚙ | EEのみ | -| [GitLab Pages](#gitlab-pages) | 静的ウェブサイトをホスト | ⚙ | ⚙ | ⚙ | ❌ | ✅ | ⚙ | ⚙ | CEとEE | -| [GitLabエージェント](#gitlab-agent) | クラウドネイティブな方法でKubernetesクラスターを統合 | ⚙ | ⚙ | ⚙ | ❌ | ❌ | ⤓ | ⚙ | EEのみ | -| [GitLab自己モニタリング: Alertmanager](#alertmanager) | Prometheusからのアラートの重複排除、グループ化、ルーティング | ⚙ | ⚙ | ✅ | ⚙ | ✅ | ❌ | ❌ | CEとEE | -| [GitLab自己モニタリング: Grafana](#grafana) | メトリクスダッシュボード | ✅ | ✅ | ⚙ | ⤓ | ✅ | ❌ | ⚙ | CEとEE | -| [GitLab自己モニタリング: Jaeger](#jaeger) | GitLabインスタンスが生成したトレースを表示 | ❌ | ⚙ | ⚙ | ❌ | ❌ | ⤓ | ⚙ | CEとEE | -| [GitLab自己モニタリング: Prometheus](#prometheus) | 時系列データベース、メトリクス収集、クエリサービス | ✅ | ✅ | ✅ | ⚙ | ✅ | ❌ | ⚙ | CEとEE | -| [GitLab自己モニタリング: Sentry](#sentry) | GitLabインスタンスが生成したエラーを追跡 | ⤓ | ⤓ | ⤓ | ❌ | ✅ | ⤓ | ⤓ | CEとEE | -| [GitLab Shell](#gitlab-shell) | SSHセッションで`git`を処理 | ✅ | ✅ | ✅ | ✅ | ✅ | ⚙ | ✅ | CEとEE | -| [GitLab Workhorse](#gitlab-workhorse) | スマートリバースプロキシ、大規模なHTTPリクエストを処理 | ✅ | ✅ | ✅ | ✅ | ✅ | ⚙ | ✅ | CEとEE | -| [受信メール（SMTP）](#inbound-email) | イシューを更新するメッセージを受信 | ⤓ | ⤓ | ⚙ | ⤓ | ✅ | ⤓ | ⤓ | CEとEE | -| [Jaegerインテグレーション](#jaeger) | デプロイしたアプリの分散トレーシング | ⤓ | ⤓ | ⤓ | ⤓ | ⤓ | ⤓ | ⚙ | EEのみ | -| [LDAP認証](#ldap-authentication) | 一元化されたLDAPディレクトリのユーザーを認証 | ⤓ | ⤓ | ⤓ | ⤓ | ❌ | ⤓ | ⚙ | CEとEE | -| [Mattermost](#mattermost) | オープンソースのSlackの代替 | ⚙ | ⚙ | ⤓ | ⤓ | ⤓ | ❌ | ⚙ | CEとEE | -| [MinIO](#minio) | オブジェクトストレージサービス | ⤓ | ⤓ | ✅ | ✅ | ✅ | ❌ | ⚙ | CEとEE | -| [NGINX](#nginx) | リクエストを適切なコンポーネントにルーティングし、SSLを終端 | ✅ | ✅ | ✅ | ⚙ | ✅ | ⤓ | ⚙ | CEとEE | -| [ノードExporter](#node-exporter) | システムメトリクスを含むPrometheusエンドポイント | ✅ | ✅ | N/A | N/A | ✅ | ❌ | ❌ | CEとEE | -| [送信メール（SMTP）](#outbound-email) | ユーザーにメールメッセージを送信 | ⤓ | ⤓ | ⚙ | ⤓ | ✅ | ⤓ | ⤓ | CEとEE | -| [Patroni](#patroni) | PostgreSQL HAクラスターのリーダー選択とレプリケーションを管理 | ⚙ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | EEのみ | -| [PgBouncer Exporter](#pgbouncer-exporter) | PgBouncerメトリクスを含むPrometheusエンドポイント | ⚙ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | CEとEE | -| [PgBouncer](#pgbouncer) | データベース接続プーリング、フェイルオーバー | ⚙ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | EEのみ | -| [PostgreSQL Exporter](#postgresql-exporter) | PostgreSQLメトリクスを含むPrometheusエンドポイント | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | CEとEE | -| [PostgreSQL](#postgresql) | データベース | ✅ | ✅ | ✅ | ✅ | ✅ | ⤓ | ✅ | CEとEE | -| [Praefect](#praefect) | GitクライアントとGitalyストレージノード間の透過型プロキシ。 | ✅ | ✅ | ⚙ | ❌ | ❌ | ⚙ | ✅ | CEとEE | -| [Puma（GitLab Rails）](#puma) | WebインターフェースとAPI間のリクエストを処理 | ✅ | ✅ | ✅ | ✅ | ✅ | ⚙ | ✅ | CEとEE | -| [Redis Exporter](#redis-exporter) | Redisメトリクスを含むPrometheusエンドポイント | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | CEとEE | -| [Redis](#redis) | キャッシュサービス | ✅ | ✅ | ✅ | ✅ | ✅ | ⤓ | ✅ | CEとEE | -| [レジストリ](#registry) | コンテナレジストリ。イメージのプッシュとプルを許可 | ⚙ | ⚙ | ✅ | ✅ | ✅ | ⤓ | ⚙ | CEとEE | -| [Runner](#gitlab-runner) | GitLab CI/CDジョブを実行 | ⤓ | ⤓ | ✅ | ⚙ | ✅ | ⚙ | ⚙ | CEとEE | -| [Sentryインテグレーション](#sentry) | デプロイしたアプリのエラー追跡 | ⤓ | ⤓ | ⤓ | ⤓ | ⤓ | ⤓ | ⤓ | CEとEE | -| [Sidekiq](#sidekiq) | バックグラウンドジョブプロセッサ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | CEとEE | -| [トークン失効API](sec/token_revocation_api.md) | 流出したシークレットを受信して失効させる | ❌ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | EEのみ | - -### コンポーネントの詳細 - -このドキュメントは、GitLabの内部構造とその連携方法について、より深く理解したいシステム管理者やGitLabサポートエンジニアによる利用を想定して作成しています。 - -デプロイ時、GitLabは以下のプロセスの集合体と見なす必要があります。トラブルシューティングまたはデバッグを行う際は、どのコンポーネントを参照しているかを可能な限り特定します。それで明確性が向上し、混乱を軽減します。 - -**レイヤ** - -GitLabは、プロセスの観点からは2つのレイヤを持つと考えることができます。 - -- **モニタリング**: このレイヤのものはGitLabアプリケーションの提供には不要ですが、管理者はインフラストラクチャやサービス全体の動作についてより深く知ることができます。 -- **コア**: プラットフォームとしてのGitLabの提供に不可欠なプロセス。このプロセスのいずれかが停止すると、GitLabが停止します。コアレイヤは、さらに以下に分類できます。 - - **プロセッサ**: このプロセスは実際に操作を実行し、サービスを提供する機能を分担しています。 - - **データ**: このサービスはGitLabサービス用に構造化されたデータを保存/公開します。 - -#### Alertmanager - -- [プロジェクトページ](https://github.com/prometheus/alertmanager/blob/main/README.md) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template) - - [チャート](https://github.com/helm/charts/tree/master/stable/prometheus) -- レイヤ: モニタリング -- プロセス: `alertmanager` -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -[Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)はPrometheusが提供するツールで、_Prometheusサーバーなどのクライアントアプリケーションが送信したアラートを処理します。メール、PagerDuty、Opsgenieなどの適切な受信側インテグレーションへの重複排除、グループ化、ルーティングを行います。また、アラートのサイレント化と禁止も行います。_アラートの内容については、[イシュー#45740](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45740)をご覧ください。 - -#### 証明書管理 - -- プロジェクトページ: - - [Omnibus](https://github.com/certbot/certbot/blob/master/README.rst) - - [チャート](https://github.com/cert-manager/cert-manager/blob/master/README.md) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/ssl/) - - [チャート](https://docs.gitlab.com/charts/installation/tls.html) - - [ソース](../install/installation.md#using-https) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/nginx.md) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [シークレット管理](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/#secrets-management) - -#### Consul - -- [プロジェクトページ](https://github.com/hashicorp/consul/blob/main/README.md) -- 設定: - - [Omnibus](../administration/consul.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#postgresql) -- レイヤ: コアサービス（データ） -- GitLab.com: [Consul](../user/gitlab_com/_index.md#consul) - -Consulは、サービスディスカバリと設定のためのツールです。Consulは分散型で可用性が高く、高度にスケーラブルです。 - -#### データベースの移行 - -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/database.html#disabling-automatic-database-migration) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/migrations/) - - [ソース](../update/upgrading_from_source.md#install-libraries-and-run-migrations) -- レイヤ: コアサービス（データ） - -#### Elasticsearch - -- [プロジェクトページ](https://github.com/elastic/elasticsearch/) -- 設定: - - [Omnibus](../integration/advanced_search/elasticsearch.md) - - [チャート](../integration/advanced_search/elasticsearch.md) - - [ソース](../integration/advanced_search/elasticsearch.md) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/elasticsearch.md) -- レイヤ: コアサービス（データ） -- GitLab.com: [GitLab.comでの高度な検索の動作（完了）](https://gitlab.com/groups/gitlab-org/-/epics/153) エピックを取得します。 - -Elasticsearchは、クラウド向けに構築された分散RESTful検索エンジンです。 - -#### Gitaly - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitaly/blob/master/README.md) -- 設定: - - [Omnibus](../administration/gitaly/_index.md) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/gitaly/) - - [ソース](../install/installation.md#install-gitaly) -- レイヤ: コアサービス（データ） -- プロセス: `gitaly` - -Gitalyは、GitLabの分散デプロイ（GitLab.comやHA（高可用性）デプロイなど）においてGitストレージにNFSを必要としないように、GitLabが設計したサービスです。11.3.0の時点で、このサービスはGitLabでのすべてのGitレベルのアクセスを処理します。このプロジェクトの詳細については、[プロジェクトのREADME](https://gitlab.com/gitlab-org/gitaly)を参照してください。 - -#### Praefect - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitaly/blob/master/README.md) -- 設定: - - [Omnibus](../administration/gitaly/_index.md) - - [ソース](../install/installation.md#install-gitaly) -- レイヤ: コアサービス（データ） -- プロセス: `praefect` - -Praefectは、各GitクライアントとGitaly間の透過型プロキシで、セカンダリノードへのリポジトリの更新のレプリケーションを調整します。 - -#### GitLab Geo - -- 設定: - - [Omnibus](../administration/geo/setup/_index.md) - - [チャート](https://docs.gitlab.com/charts/advanced/geo/) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/geo.md) -- レイヤ: コアサービス（プロセッサ） - -Geoは、プライマリGitLabインスタンスの1つ以上の読み取り専用ミラーを提供して、分散したチームによる開発を高速化するように構築した高度な機能です。このミラー（Geoセカンダリサイト）は、大規模なリポジトリやプロジェクトのクローンやフェッチにかかる時間を短縮したり、ディザスタリカバリソリューションの一部にしたりできます。 - -#### GitLab Exporter - -- [プロジェクトページ](https://gitlab.com/gitlab-org/ruby/gems/gitlab-exporter) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/gitlab_exporter.md) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/gitlab-exporter/) -- レイヤ: モニタリング -- プロセス: `gitlab-exporter` -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -GitLab Exporterは、GitLabアプリケーションの内部に関するメトリクスをPrometheusにエクスポートできるように、社内で設計したプロセスです。詳細については[プロジェクトのREADME](https://gitlab.com/gitlab-org/ruby/gems/gitlab-exporter)を参照してください。 - -#### GitLabエージェント - -- [プロジェクトページ](https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/kas/) - -[GitLabエージェント](../user/clusters/agent/_index.md)は、安全かつクラウドネイティブな方法でGitLabとKubernetesの統合タスクを解決するための、アクティブなインクラスターコンポーネントです。 - -これを使用して、Kubernetesクラスターへのデプロイを同期できます。 - -#### GitLab Pages - -- 設定: - - [Omnibus](../administration/pages/_index.md) - - [チャート](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/37) - - [ソース](../install/installation.md#install-gitlab-pages) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/pages.md) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [GitLab Pages](../user/gitlab_com/_index.md#gitlab-pages) - -GitLab Pagesは、GitLabのリポジトリから静的ウェブサイトを直接公開できる機能です。 - -ポートフォリオ、ドキュメント、マニフェスト、ビジネスプレゼンテーションなど、個人用またはビジネス用のウェブサイトのいずれかに使用できます。コンテンツにライセンスを付与することもできます。 - -#### GitLab Runner - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitlab-runner/blob/main/README.md) -- 設定: - - [Omnibus](https://docs.gitlab.com/runner/) - - [チャート](https://docs.gitlab.com/runner/install/kubernetes.html) - - [ソース](https://docs.gitlab.com/runner/) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/runner.md) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [Runner](../ci/runners/_index.md) - -GitLab Runnerはジョブを実行し、結果をGitLabに送信します。 - -GitLab CI/CDは、GitLabに含まれているオープンソースの継続的インテグレーションサービスであり、テストを統合します。このプロジェクトの以前の名前は`GitLab CI Multi Runner`でしたが、今後は`GitLab Runner`（CIなし）を使用します。 - -#### GitLab Shell - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitlab-shell/) -- [ドキュメント](gitlab_shell/_index.md) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/gitlab-shell/) - - [ソース](../install/installation.md#install-gitlab-shell) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: コアサービス（プロセッサ） - -[GitLab Shell](gitlab_shell/_index.md)はGitLabで設計したプログラムで、SSHベースの`git`セッションを処理し、許可されたキーのリストを変更します。GitLab ShellはUnixシェルではなく、BashやZshの代替でもありません。 - -#### GitLab Workhorse - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/workhorse/index.md) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/webservice/) - - [ソース](../install/installation.md#install-gitlab-workhorse) -- レイヤ: コアサービス（プロセッサ） -- プロセス: `gitlab-workhorse` - -[GitLab Workhorse](https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/development/workhorse)はGitLabで設計したプログラムで、Pumaからの圧力を軽減します。[開発の歴史的理由](https://about.gitlab.com/blog/2016/04/12/a-brief-history-of-gitlab-workhorse/)を参照してください。GitLab全体を高速化するための、スマートリバースプロキシとして機能するように設計しています。 - -#### Grafana - -- [プロジェクトページ](https://github.com/grafana/grafana/blob/master/README.md) -- 設定: - - [Omnibus](../administration/monitoring/performance/grafana_configuration.md) - - [チャート](https://docs.gitlab.com/charts/charts/globals#configure-grafana-integration) -- レイヤ: モニタリング -- GitLab.com: [GitLabトリアージGrafanaダッシュボード](https://dashboards.gitlab.com/d/RZmbBr7mk/gitlab-triage?refresh=30s) - -Grafanaは、Graphite、Elasticsearch、OpenTSDB、Prometheus、InfluxDB用の、オープンソースで機能豊富なメトリクスダッシュボードおよびグラフエディタです。 - -#### Jaeger - -- [プロジェクトページ](https://github.com/jaegertracing/jaeger/blob/main/README.md) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4104) - - [チャート](https://docs.gitlab.com/charts/charts/globals#tracing) - - [ソース](distributed_tracing.md#enabling-distributed-tracing) - - [GitLab Development Kit（GDK）](distributed_tracing.md#using-jaeger-in-the-gitlab-development-kit) -- レイヤ: モニタリング -- GitLab.com: [GitLabインスタンスのトレーシングを有効化する設定](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4104)のイシュー。 - -DapperとOpenZipkinに触発されたJaegerは、分散トレーシングシステムです。マイクロサービスベースの分散システムの監視に使用できます。 - -#### Logrotate - -- [プロジェクトページ](https://github.com/logrotate/logrotate/blob/main/README.md) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/logs.html#logrotate) -- レイヤ: コアサービス -- プロセス: `logrotate` - -GitLabは、すべてをログに記録する多数のサービスで構成されています。独自のLogrotateをバンドルし、責任を持ってログ記録を確認しています。これは一般的なオープンソース製品の単なるパッケージ化バージョンです。 - -#### Mattermost - -- [プロジェクトページ](https://github.com/mattermost/mattermost/blob/master/README.md) -- 設定: - - [Omnibus](../integration/mattermost/_index.md) - - [チャート](https://docs.mattermost.com/install/install-mmte-helm-gitlab-helm.html) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [Mattermost](../user/project/integrations/mattermost.md) - -Mattermostはによる、オープンソースのプライベートクラウドによるSlack代替品です。 - -#### MinIO - -- [プロジェクトページ](https://github.com/minio/minio/blob/master/README.md) -- 設定: - - [Omnibus](https://min.io/download) - - [チャート](https://docs.gitlab.com/charts/charts/minio/) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/object_storage.md) -- レイヤ: コアサービス（データ） -- GitLab.com: [ストレージアーキテクチャ](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/#storage-architecture) - -MinIOは、GNU AGPL v3.0の下でリリースされたオブジェクトストレージサーバーです。Amazon S3 Cloud Storageサービスと互換性があります。写真、ビデオ、ログファイル、バックアップ、コンテナ/VMイメージなどの非構造化データの保存に最適です。オブジェクトのサイズは数KBから最大5 TBまでです。 - -#### NGINX - -- プロジェクトページ: - - [Omnibus](https://github.com/nginx/nginx) - - [チャート](https://github.com/kubernetes/ingress-nginx/blob/main/README.md) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/nginx.html) - - [チャート](https://docs.gitlab.com/charts/charts/nginx/) - - [ソース](../install/installation.md#10-nginx) -- レイヤ: コアサービス（プロセッサ） -- プロセス: `nginx` - -NGINXには、すべてのHTTPリクエストのIngressポートがあり、GitLab内の適切なサブシステムにルーティングします。一般的なオープンソースのWebサーバーの未変更バージョンをバンドルしています。 - -#### ノードExporter - -- [プロジェクトページ](https://github.com/prometheus/node_exporter/blob/master/README.md) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/node_exporter.md) - - [チャート](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1332) -- レイヤ: モニタリング -- プロセス: `node-exporter` -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -[Node Exporter](https://github.com/prometheus/node_exporter)はPrometheusのツールで、基盤となるマシン（CPU /ディスク/ロードなど）にメトリクスを提供します。これはPrometheusプロジェクトからの一般的なオープンソース製品の、単なるパッケージ化バージョンです。 - -#### Patroni - -- [プロジェクトページ](https://github.com/patroni/patroni) -- 設定: - - [Omnibus](../administration/postgresql/replication_and_failover.md#patroni) -- レイヤ: コアサービス（データ） -- プロセス: `patroni` -- GitLab.com: [データベースアーキテクチャ](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/#database-architecture) - -#### PgBouncer - -- [プロジェクトページ](https://github.com/pgbouncer/pgbouncer/blob/master/README.md) -- 設定: - - [Omnibus](../administration/postgresql/pgbouncer.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#postgresql) -- レイヤ: コアサービス（データ） -- GitLab.com: [データベースアーキテクチャ](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/#database-architecture) - -PostgreSQL用の軽量コネクションプーラー。 - -#### PgBouncer Exporter - -- [プロジェクトページ](https://github.com/prometheus-community/pgbouncer_exporter/blob/master/README.md) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/pgbouncer_exporter.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#postgresql) -- レイヤ: モニタリング -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -PgBouncer用Prometheus exporter。9127/メトリクスでメトリクスをエクスポートします。 - -#### PostgreSQL - -- [プロジェクトページ](https://github.com/postgres/postgres/) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/database.html) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#postgresql) - - [ソース](../install/installation.md#7-database) -- レイヤ: コアサービス（データ） -- プロセス: `postgresql` -- GitLab.com: [PostgreSQL](https://handbook.gitlab.com/handbook/engineering/infrastructure/database/) - -GitLabは一般的なデータベースをパッケージ化し、アプリケーションのメタデータとユーザー情報のストレージを提供しています。 - -#### PostgreSQL Exporter - -- [プロジェクトページ](https://github.com/prometheus-community/postgres_exporter/blob/master/README.md) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/postgres_exporter.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#postgresql) -- レイヤ: モニタリング -- プロセス: `postgres-exporter` -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -[`postgres_exporter`](https://github.com/prometheus-community/postgres_exporter)はコミュニティが提供するPrometheus exporterで、Grafanaダッシュボードで使用するためにPostgreSQLに関するデータをPrometheusに提供します。 - -#### Prometheus - -- [プロジェクトページ](https://github.com/prometheus/prometheus/blob/main/README.md) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/_index.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#prometheus) -- レイヤ: モニタリング -- プロセス: `prometheus` -- GitLab.com: [Prometheus](../user/gitlab_com/_index.md#prometheus) - -Prometheusは時系列ツールで、GitLab管理者がGitLabサービスを提供する際に使用する、個別のプロセスに関するメトリクスの公開に役立ちます。 - -#### Redis - -- [プロジェクトページ](https://github.com/redis/redis/blob/unstable/README.md) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/redis.html) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#redis) - - [ソース](../install/installation.md#8-redis) -- レイヤ: コアサービス（データ） -- プロセス: `redis` - -Redisは、以下の情報を格納する場所を提供するようパッケージ化しています。 - -- セッションデータ -- 一時キャッシュ情報 -- バックグラウンドジョブキュー - -GitLabでのRedisの使用方法の詳細については、[Redisガイドライン](redis.md)を参照してください。 - -#### Redis Exporter - -- [プロジェクトページ](https://github.com/oliver006/redis_exporter/blob/master/README.md) -- 設定: - - [Omnibus](../administration/monitoring/prometheus/redis_exporter.md) - - [チャート](https://docs.gitlab.com/charts/installation/deployment.html#redis) -- レイヤ: モニタリング -- プロセス: `redis-exporter` -- GitLab.com: [GitLab.comのモニタリング](https://handbook.gitlab.com/handbook/engineering/monitoring/) - -[Redis Exporter](https://github.com/oliver006/redis_exporter)は、Redisプロセスに関する特定のメトリクスをPrometheusに提供し、そのメトリクスをGrafanaでグラフ化できるように設計しています。 - -#### レジストリ - -- [プロジェクトページ](https://gitlab.com/gitlab-org/container-registry) -- 設定: - - [Omnibus](../administration/packages/container_registry.md) - - [チャート](https://docs.gitlab.com/charts/charts/registry/) - - [ソース](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md?ref_type=heads) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/registry.md) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [GitLabコンテナレジストリ](../user/packages/container_registry/build_and_push_images.md#use-gitlab-cicd) - -レジストリは、ユーザーが独自のDockerイメージを保存する際に使用します。バンドルしているレジストリは、ロードバランサーとしてNGINXを、認証マネージャーとしてGitLabを使用します。クライアントがレジストリからイメージをプルまたはプッシュするリクエストを行うたびに、`401`レスポンスと、認証トークンを取得する場所（この場合はGitLabインスタンス）を詳細に指定するヘッダーを返します。その後クライアントはGitLabからプルまたはプッシュ認証トークンをリクエストし、レジストリへの元のリクエストを再試行します。詳細については、[トークン認証](https://distribution.github.io/distribution/spec/auth/token/)を参照してください。 - -外部レジストリも、GitLabを認証エンドポイントとして使用するように設定できます。 - -#### Sentry - -- [プロジェクトページ](https://github.com/getsentry/sentry/) -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/configuration.html#error-reporting-and-logging-with-sentry) - - [チャート](https://docs.gitlab.com/charts/charts/globals#sentry-settings) - - [ソース](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: モニタリング -- GitLab.com: [Sentryの検索](https://handbook.gitlab.com/handbook/support/workflows/500_errors/#searching-sentry) - -Sentryは基本的に、リアルタイムでクラッシュを監視し修正するのに役立つサービスです。サーバーはPythonで記述されていますが、どのアプリケーションでも任意の言語からイベントを送信する完全なAPIを装備しています。 - -デプロイしたアプリのモニタリングについては、[Sentryインテグレーションドキュメント](../operations/error_tracking.md)を参照してください - -#### Sidekiq - -- [プロジェクトページ](https://github.com/sidekiq/sidekiq/blob/main/README.md) -- 設定: - - [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/sidekiq/) - - [minikube Minimal](https://docs.gitlab.com/charts/charts/gitlab/sidekiq/) - - [ソース](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: コアサービス（プロセッサ） -- プロセス: `sidekiq` -- GitLab.com: [Sidekiq](../user/gitlab_com/_index.md#sidekiq) - -Sidekiqは、Redisキューからジョブをプルして処理するRubyバックグラウンドジョブプロセッサです。バックグラウンドジョブを使用すると、GitLabは作業をバックグラウンドに移行して、より高速なリクエスト/レスポンスサイクルを提供できます。 - -#### Puma - -GitLab 13.0以降、PumaがデフォルトのWebサーバーです。 - -- [プロジェクトページ](https://gitlab.com/gitlab-org/gitlab/-/blob/master/README.md) -- 設定: - - [Omnibus](../administration/operations/puma.md) - - [チャート](https://docs.gitlab.com/charts/charts/gitlab/webservice/) - - [ソース](../install/installation.md#configure-it) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: コアサービス（プロセッサ） -- プロセス: `puma` -- GitLab.com: [Puma](../user/gitlab_com/_index.md#puma) - -[Puma](https://puma.io/)はRubyアプリケーションサーバーで、GitLabでユーザー向け機能を提供するコアRailsアプリケーションの実行に使用します。これはGitLabのバージョンによっては、しばしばプロセス出力に`bundle`または`config.ru`と表示されます。 - -#### LDAP認証 - -- 設定: - - [Omnibus](../administration/auth/ldap/_index.md) - - [チャート](https://docs.gitlab.com/charts/charts/globals.html#ldap) - - [ソース](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/main/doc/howto/ldap.md) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [製品プラン](https://about.gitlab.com/pricing/#gitlab-com) - -#### 送信メール - -- 設定: - - [Omnibus](https://docs.gitlab.com/omnibus/settings/smtp.html) - - [チャート](https://docs.gitlab.com/charts/installation/command-line-options.html#outgoing-email-configuration) - - [ソース](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [メール設定](../user/gitlab_com/_index.md#email) - -#### 受信メール - -- 設定: - - [Omnibus](../administration/incoming_email.md) - - [チャート](https://docs.gitlab.com/charts/installation/command-line-options.html#incoming-email-configuration) - - [ソース](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) - - [GitLab Development Kit（GDK）](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/gitlab.yml.example) -- レイヤ: コアサービス（プロセッサ） -- GitLab.com: [メール設定](../user/gitlab_com/_index.md#email) - -## リクエストタイプ別のGitLab - -GitLabは、エンドユーザーがサービスにアクセスするための2つの「インターフェース」を提供します。 - -- Web HTTPリクエスト（UI/APIの表示） -- Git HTTP/SSHリクエスト（Gitデータのプッシュ/プル） - -一部のプロセスは両方に、その他のプロセスは排他的に特定のタイプのリクエストに使用されるため、この区別を理解することが重要です。 - -### GitLab Web HTTPリクエストサイクル - -HTTPエンドポイント（`/users/sign_in`など）にリクエストを行う場合、リクエストはGitLabサービスを介して次のパスを通過します。 - -- NGINX - 最初の行のリバースプロキシとして機能します。 -- GitLab Workhorse - これでRailsアプリケーションや他の場所にアクセスする必要があるかを判断し、Pumaへの負荷を軽減します。 -- Puma - Webリクエストであればアプリケーションにアクセスする必要があるため、Pumaにルーティングされます。 -- PostgreSQL/Gitaly/Redis - リクエストの種類によっては、これらのサービスにアクセスしてデータを保存または取得します。 - -### GitLab Gitリクエストサイクル - -以下に、HTTPとSSH Gitリクエストが実行されるさまざまなパスについて説明します。Webリクエストサイクルと一部重複する部分もありますが、異なる部分もあります。 - -### Webリクエスト（80/443） - -HTTP経由のGitオペレーションは、[Gitドキュメント](https://git-scm.com/docs/http-protocol)で説明しているステートレスな「スマート」プロトコルを使用していますが、このオペレーションを処理する責任は、複数のGitLabコンポーネントに分散されます。 - -これは`git fetch`のシーケンス図です。すべてのリクエストはNGINXと他のHTTPロードバランサーを通過しますが、何らかの方法でそれらが変換されることはありません。すべてのパスは`/namespace/project.git`のURLからの相対パスとして表示されます。 - -```mermaid -sequenceDiagram - participant Git on client - participant NGINX - participant Workhorse - participant Rails - participant Gitaly - participant Git on server - - Note left of Git on client: git fetch
info-refs - Git on client->>+Workhorse: GET /info/refs?service=git-upload-pack - Workhorse->>+Rails: GET /info/refs?service=git-upload-pack - Note right of Rails: Auth check - Rails-->>-Workhorse: Gitlab::Workhorse.git_http_ok - Workhorse->>+Gitaly: SmartHTTPService.InfoRefsUploadPack request - Gitaly->>+Git on server: git upload-pack --stateless-rpc --advertise-refs - Git on server-->>-Gitaly: git upload-pack response - Gitaly-->>-Workhorse: SmartHTTPService.InfoRefsUploadPack response - Workhorse-->>-Git on client: 200 OK - - Note left of Git on client: git fetch
fetch-pack - Git on client->>+Workhorse: POST /git-upload-pack - Workhorse->>+Rails: POST /git-upload-pack - Note right of Rails: Auth check - Rails-->>-Workhorse: Gitlab::Workhorse.git_http_ok - Workhorse->>+Gitaly: SmartHTTPService.PostUploadPack request - Gitaly->>+Git on server: git upload-pack --stateless-rpc - Git on server-->>-Gitaly: git upload-pack response - Gitaly-->>-Workhorse: SmartHTTPService.PostUploadPack response - Workhorse-->>-Git on client: 200 OK -``` - -`git push`の場合もシーケンスはほぼ同じですが、`git-upload-pack`の代わりに`git-receive-pack`を使用します。 - -### SSHリクエスト（22） - -SSHでのGitオペレーションは、[Gitドキュメント](https://git-scm.com/docs/pack-protocol#_ssh_transport)で説明しているステートフルなプロトコルを使用できますが、それを処理する責任は、複数のGitLabコンポーネントに分散されます。 - -GitLabコンポーネントはSSHを直接認識しません。すべてのSSH接続は、クライアントマシン上のGitとSSHサーバーの間で行い、SSHサーバーが接続を終了させます。SSHサーバーは、すべての接続を`git`ユーザーとして認証します。GitLabユーザーは、クライアントが提示したSSHキーで区別します。 - -これは`git fetch`のシーケンス図で、[高速SSHキー検索](../administration/operations/fast_ssh_key_lookup.md)が有効になっていると仮定しています。`AuthorizedKeysCommand`は[GitLab Shell](#gitlab-shell)が提供する実行可能ファイルです。 - -```mermaid -sequenceDiagram - participant Git on client - participant SSH server - participant AuthorizedKeysCommand - participant GitLab Shell - participant Rails - participant Gitaly - participant Git on server - - Note left of Git on client: git fetch - Git on client->>+SSH server: ssh git fetch-pack request - SSH server->>+AuthorizedKeysCommand: gitlab-shell-authorized-keys-check git AAAA... - AuthorizedKeysCommand->>+Rails: GET /internal/api/authorized_keys?key=AAAA... - Note right of Rails: Lookup key ID - Rails-->>-AuthorizedKeysCommand: 200 OK, command="gitlab-shell upload-pack key_id=1" - AuthorizedKeysCommand-->>-SSH server: command="gitlab-shell upload-pack key_id=1" - SSH server->>+GitLab Shell: gitlab-shell upload-pack key_id=1 - GitLab Shell->>+Rails: GET /internal/api/allowed?action=upload_pack&key_id=1 - Note right of Rails: Auth check - Rails-->>-GitLab Shell: 200 OK, { gitaly: ... } - GitLab Shell->>+Gitaly: SSHService.SSHUploadPack request - Gitaly->>+Git on server: git upload-pack request - Note over Git on client,Git on server: Bidirectional communication between Git client and server - Git on server-->>-Gitaly: git upload-pack response - Gitaly -->>-GitLab Shell: SSHService.SSHUploadPack response - GitLab Shell-->>-SSH server: gitlab-shell upload-pack response - SSH server-->>-Git on client: ssh git fetch-pack response -``` - -`git push`オペレーションは非常によく似ていますが、`git upload-pack`の代わりに`git receive-pack`を使用します。 - -高速SSHキー検索が有効になっていない場合、SSHサーバーは`~git/.ssh/authorized_keys`ファイルを読んで、特定のSSHセッションで実行するコマンドを決定します。これはユーザーがSSHキーを変更するたびに実行するようにスケジュールした、Railsの[`AuthorizedKeysWorker`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/workers/authorized_keys_worker.rb)が最新の状態に保ちます。 - -[SSH証明書](../administration/operations/ssh_certificates.md)はキーの代わりに使用できます。この場合、`AuthorizedKeysCommand`は`AuthorizedPrincipalsCommand`に置き換えられます。こうしてRailsの内部APIを使用せずに証明書からユーザー名を抽出します。これは後ほど`key_id`の代わりに[`/api/internal/allowed`](internal_api/_index.md)コールで使用します。 - -GitLab Shellには2要素認証コードのリセットなど、Gitalyを必要としないオペレーションもいくつかあります。これらは同じ方法で処理しますが、Gitalyへのラウンドトリップはありません。Railsが[内部API](internal_api/_index.md)コールの一部としてアクションを実行し、GitLab Shellが応答をユーザーに直接ストリーミングして返します。 - -## システムレイアウト - -図で`~git`を参照する場合、それは通常`/home/git`であるGitユーザーのホームディレクトリを意味します。 - -GitLabは、主に`/home/git`ユーザーのホームディレクトリに`git`ユーザーとしてインストールされます。ホームディレクトリ内には、GitLabサーバーソフトウェアとリポジトリがあります（ただしリポジトリの場所は設定可能です）。 - -ベアリポジトリは`/home/git/repositories`にあります。GitLabはRuby on Railsアプリケーションであり、内部の動作の詳細は、Ruby on Railsアプリケーションの動作方法を学習すれば理解できます。 - -SSHでリポジトリを提供するには、`/home/git/gitlab-shell`にインストールしたGitLab Shellというアドオンアプリケーションが使えます。 - -### インストールフォルダーの概要 - -要約すると、これは[`git`ユーザーのホームディレクトリのディレクトリ構造](../install/installation.md#gitlab-directory-structure)です。 - -### プロセス - -```shell -ps aux | grep '^git' -``` - -GitLabには、動作させるためのコンポーネントがいくつかあります。永続化データベース（PostgreSQL）とRedisデータベースが必要で、Apache `httpd`またはNGINXを使用してPumaに`proxypass`します。これらのコンポーネントはすべて、異なるシステムユーザー（たとえば`git`ではなく`postgres`、`redis`、`www-data`など）としてGitLabに実行する必要があります。 - -`git`ユーザーとして、SidekiqとPuma（デフォルトでは`8080`ポートで実行されているシンプルなRuby HTTPサーバー）を起動します。GitLabユーザー下には通常、`puma master`（1プロセス）、`puma cluster worker`（2プロセス）、`sidekiq`（1プロセス）の4プロセスがあります。 - -### リポジトリアクセス - -リポジトリには、HTTPまたはSSH経由でアクセスできます。HTTPクローニング/プッシュ/プルはGitLab APIを使用し、SSHクローニングはGitLab Shellが処理します（前述）。 - -## トラブルシューティング - -詳細については、READMEを参照してください。 - -### サービスのInitスクリプト - -以下のGitLab initスクリプトは、PumaとSidekiqを起動/停止します。 - -```plaintext -/etc/init.d/gitlab -Usage: service gitlab {start|stop|restart|reload|status} -``` - -Redis（キー値を保存/非永続化データベース）: - -```plaintext -/etc/init.d/redis -Usage: /etc/init.d/redis {start|stop|status|restart|condrestart|try-restart} -``` - -SSHデーモン: - -```plaintext -/etc/init.d/sshd -Usage: /etc/init.d/sshd {start|stop|restart|reload|force-reload|condrestart|try-restart|status} -``` - -Webサーバー（次のいずれか）: - -```plaintext -/etc/init.d/httpd -Usage: httpd {start|stop|restart|condrestart|try-restart|force-reload|reload|status|fullstatus|graceful|help|configtest} - -$ /etc/init.d/nginx -Usage: nginx {start|stop|restart|reload|force-reload|status|configtest} -``` - -永続化データベース: - -```plaintext -$ /etc/init.d/postgresql -Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-reload|status} [version ..] -``` - -### サービスのログの場所 - -GitLab（PumaとSidekiqのログを含む）: - -- `/home/git/gitlab/log/`には通常、`application.log`、`production.log`、`sidekiq.log`、`puma.stdout.log`、`git_json.log`、`puma.stderr.log`が含まれています。 - -GitLab Shell: - -- `/home/git/gitlab-shell/gitlab-shell.log` - -SSH: - -- `/var/log/auth.log`認証ログ（Ubuntuの場合）。 -- `/var/log/secure`認証ログ（RHELの場合）。 - -NGINX: - -- `/var/log/nginx/`にはエラーログとアクセスログが含まれています。 - -Apache `httpd`: - -- [Apacheログの説明](https://httpd.apache.org/docs/2.2/logs.html)。 -- `/var/log/apache2/`にはエラーログと出力ログが含まれています（Ubuntuの場合）。 -- `/var/log/httpd/`にはエラーログと出力ログが含まれています（RHELの場合）。 - -Redis: - -- `/var/log/redis/redis.log`にはログローテーションされたログもあります。 - -PostgreSQL: - -- `/var/log/postgresql/*` - -### GitLab固有の設定ファイル - -GitLabでは`/home/git/gitlab/config/*`に設定ファイルがあります。一般的に参照される設定ファイルには次のものがあります。 - -- `gitlab.yml`: GitLab Railsの設定 -- `puma.rb`: Puma Webサーバーの設定 -- `database.yml`: データベース接続の設定 - -GitLab Shellでは`/home/git/gitlab-shell/config.yml`に設定ファイルがあります。 - -#### GitLab Railsに新しい設定を追加する - -`gitlab.yml`に属する設定には、以下に関するものがあります。 - -- 複数のサービスにわたってアプリケーションを接続する方法。たとえばGitalyアドレス、Redisアドレス、Postgresアドレス、Consulアドレスなどです。 -- 分散トレーシング設定と一部の可観測性設定。たとえばヒストグラムバケット境界などです。 -- Railsの初期化中に、おそらくはPostgres 接続を確立する前に設定する必要があるもの。 - -他の多くの設定は、`ApplicationSetting`でアプリ 自体に入れる方が適切です。通常はUIで設定を管理する方が、設定ファイルを管理するよりもユーザーエクスペリエンスが優れています。開発コストに関して言えば、`gitlab.yml`を変更する方がイテレーションが迅速に思えることがよくありますが、以下のすべてのデプロイ方法を考慮すると、見合わない可能性があります。 - -`gitlab.yml`に設定を追加する場合は、以下のようにします。 - -1. [Omnibusにも追加](https://docs.gitlab.com/omnibus/settings/gitlab.yml#adding-a-new-setting-to-gitlabyml)していることを確認します。 -1. 必要に応じて、[Chartsにも追加](https://docs.gitlab.com/charts/development/style_guide.html)していることを確認します。 -1. [GDKにも追加](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/support/templates/gitlab/config/gitlab.yml.erb)していることを確認します。 - -### メンテナンスタスク - -[GitLab](https://gitlab.com/gitlab-org/gitlab/-/tree/master)ではバージョン情報を表示したり、設定を簡単にチェックしてアプリケーション内で適切に設定されていることを確認するための、Rakeタスクを用意しています。[メンテナンスRakeタスク](../administration/raketasks/maintenance.md)を参照してください。要するに、以下を実行します。 - -```shell -sudo -i -u git -cd gitlab -bundle exec rake gitlab:env:info RAILS_ENV=production -bundle exec rake gitlab:check RAILS_ENV=production -``` - -`sudo -i -u git`または`sudo su - git`のいずれかを使用して、`git`ユーザーとしてサインインすることを推奨します。GitLab が提供する`sudo`コマンドはUbuntuでは動作しますが、RHELでは常に動作するとは限りません。 - -## GitLab.com - -[GitLab.com のアーキテクチャ](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/architecture/)は参照用として詳しく記述していますが、このアーキテクチャは数百万人のユーザーがいる場合にのみ役立ちます。 - -### AIアーキテクチャ - -[SaaSモデルゲートウェイ](ai_architecture.md)を使用して、AI搭載機能を有効化できます。 diff --git a/doc-locale/ja-jp/development/audit_event_guide/_index.md b/doc-locale/ja-jp/development/audit_event_guide/_index.md new file mode 100644 index 00000000000..d04e677025e --- /dev/null +++ b/doc-locale/ja-jp/development/audit_event_guide/_index.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Compliance +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. +title: Audit event development guidelines +--- diff --git a/doc-locale/ja-jp/development/auto_devops.md b/doc-locale/ja-jp/development/auto_devops.md new file mode 100644 index 00000000000..632578882b8 --- /dev/null +++ b/doc-locale/ja-jp/development/auto_devops.md @@ -0,0 +1,6 @@ +--- +stage: Deploy +group: Environments +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. +title: Auto DevOps development guidelines +--- diff --git a/doc-locale/ja-jp/development/avoiding_required_stops.md b/doc-locale/ja-jp/development/avoiding_required_stops.md new file mode 100644 index 00000000000..d855de2dead --- /dev/null +++ b/doc-locale/ja-jp/development/avoiding_required_stops.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Distribution +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. +title: Avoiding required stops +--- diff --git a/doc-locale/ja-jp/development/backend/create_source_code_be/_index.md b/doc-locale/ja-jp/development/backend/create_source_code_be/_index.md new file mode 100644 index 00000000000..2e6e4438d4b --- /dev/null +++ b/doc-locale/ja-jp/development/backend/create_source_code_be/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Source Code Management +--- diff --git a/doc-locale/ja-jp/development/backend/create_source_code_be/gitaly_touch_points.md b/doc-locale/ja-jp/development/backend/create_source_code_be/gitaly_touch_points.md new file mode 100644 index 00000000000..42f9d827e41 --- /dev/null +++ b/doc-locale/ja-jp/development/backend/create_source_code_be/gitaly_touch_points.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Source Code - Gitaly Touch Points +--- diff --git a/doc-locale/ja-jp/development/backend/ruby_style_guide.md b/doc-locale/ja-jp/development/backend/ruby_style_guide.md new file mode 100644 index 00000000000..358b3f3c3d4 --- /dev/null +++ b/doc-locale/ja-jp/development/backend/ruby_style_guide.md @@ -0,0 +1,6 @@ +--- +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. +title: Ruby style guide +--- diff --git a/doc-locale/ja-jp/development/backup_and_restore/backup_gitlab.md b/doc-locale/ja-jp/development/backup_and_restore/backup_gitlab.md new file mode 100644 index 00000000000..5258873482a --- /dev/null +++ b/doc-locale/ja-jp/development/backup_and_restore/backup_gitlab.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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 +title: How GitLab backups work? +--- diff --git a/doc-locale/ja-jp/development/bitbucket_cloud_importer.md b/doc-locale/ja-jp/development/bitbucket_cloud_importer.md new file mode 100644 index 00000000000..42d405164e1 --- /dev/null +++ b/doc-locale/ja-jp/development/bitbucket_cloud_importer.md @@ -0,0 +1,6 @@ +--- +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. +title: Bitbucket Cloud importer developer documentation +--- diff --git a/doc-locale/ja-jp/development/bitbucket_server_importer.md b/doc-locale/ja-jp/development/bitbucket_server_importer.md new file mode 100644 index 00000000000..98171b82643 --- /dev/null +++ b/doc-locale/ja-jp/development/bitbucket_server_importer.md @@ -0,0 +1,6 @@ +--- +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. +title: Bitbucket Server importer developer documentation +--- diff --git a/doc-locale/ja-jp/development/build_test_package.md b/doc-locale/ja-jp/development/build_test_package.md new file mode 100644 index 00000000000..57d625b8a1e --- /dev/null +++ b/doc-locale/ja-jp/development/build_test_package.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Distribution +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. +title: Building a package for testing +--- diff --git a/doc-locale/ja-jp/development/bulk_import.md b/doc-locale/ja-jp/development/bulk_import.md new file mode 100644 index 00000000000..64eed67317d --- /dev/null +++ b/doc-locale/ja-jp/development/bulk_import.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Group migration by direct transfer +--- diff --git a/doc-locale/ja-jp/development/bulk_imports/contributing.md b/doc-locale/ja-jp/development/bulk_imports/contributing.md new file mode 100644 index 00000000000..42daf88d5a9 --- /dev/null +++ b/doc-locale/ja-jp/development/bulk_imports/contributing.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Add new relations to the direct transfer importer +--- diff --git a/doc-locale/ja-jp/development/cached_queries.md b/doc-locale/ja-jp/development/cached_queries.md new file mode 100644 index 00000000000..9e48dc62258 --- /dev/null +++ b/doc-locale/ja-jp/development/cached_queries.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Cloud Connector +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. +title: Cached queries guidelines +--- diff --git a/doc-locale/ja-jp/development/caching.md b/doc-locale/ja-jp/development/caching.md new file mode 100644 index 00000000000..5bbe38914ae --- /dev/null +++ b/doc-locale/ja-jp/development/caching.md @@ -0,0 +1,6 @@ +--- +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. +title: Caching guidelines +--- diff --git a/doc-locale/ja-jp/development/cascading_settings.md b/doc-locale/ja-jp/development/cascading_settings.md new file mode 100644 index 00000000000..c1f4216ce61 --- /dev/null +++ b/doc-locale/ja-jp/development/cascading_settings.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Personal Productivity +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. +title: Cascading Settings +--- diff --git a/doc-locale/ja-jp/development/cells/_index.md b/doc-locale/ja-jp/development/cells/_index.md new file mode 100644 index 00000000000..bc0886f7d76 --- /dev/null +++ b/doc-locale/ja-jp/development/cells/_index.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Cells Infrastructure +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. +title: GitLab Cells Development Guidelines +--- diff --git a/doc-locale/ja-jp/development/cells/application_settings_analysis.md b/doc-locale/ja-jp/development/cells/application_settings_analysis.md new file mode 100644 index 00000000000..0fa017756cd --- /dev/null +++ b/doc-locale/ja-jp/development/cells/application_settings_analysis.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Cells Infrastructure +info: Analysis of Application Settings for Cells 1.0. +title: Application Settings analysis +--- diff --git a/doc-locale/ja-jp/development/cells/configuration.md b/doc-locale/ja-jp/development/cells/configuration.md new file mode 100644 index 00000000000..e2c59b9feef --- /dev/null +++ b/doc-locale/ja-jp/development/cells/configuration.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Cells Infrastructure +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. +title: Configuration +--- diff --git a/doc-locale/ja-jp/development/cells/topology_service.md b/doc-locale/ja-jp/development/cells/topology_service.md new file mode 100644 index 00000000000..7bac8ec90ef --- /dev/null +++ b/doc-locale/ja-jp/development/cells/topology_service.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Cells Infrastructure +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. +title: Topology Service +--- diff --git a/doc-locale/ja-jp/development/changelog.md b/doc-locale/ja-jp/development/changelog.md index 1eb9e7fc5d0..c5f670a2046 100644 --- a/doc-locale/ja-jp/development/changelog.md +++ b/doc-locale/ja-jp/development/changelog.md @@ -2,155 +2,5 @@ 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. -title: 変更履歴エントリ +title: Changelog entries --- - -このガイドでは、変更履歴エントリファイルを生成するタイミングと方法、および変更履歴プロセスに関する情報と履歴について説明します。 - -## 概要 - -[`CHANGELOG.md`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/CHANGELOG.md)ファイル内の各リスト項目、または**エントリ**は、Gitコミットのサブジェクト行から生成します。`Changelog` [Gitトレーラー](https://git-scm.com/docs/git-interpret-trailers)を収容できる場合には、コミットを含みます。変更履歴の生成時には、作成者とマージリクエストの詳細を自動的に追加します。 - -`Changelog`トレーラーは、次の値を受け入れます。 - -- `added`:新機能 -- `fixed`:バグ修正 -- `changed`:機能変更 -- `deprecated`:新規非推奨 -- `removed`:機能削除 -- `security`:セキュリティ修正 -- `performance`:パフォーマンス改善 -- `other`:その他 - -変更履歴に含めるGitコミットの例を次に示します。 - -```plaintext -Update git vendor to gitlab - -Now that we are using gitaly to compile git, the git version isn't known -from the manifest, instead we are getting the gitaly version. Update our -vendor field to be `gitlab` to avoid cve matching old versions. - -Changelog: changed -``` - -マージリクエストに複数のコミットがある場合、[`Changelog`エントリを最初のコミットに追加していることを確認します](changelog.md#how-to-generate-a-changelog-entry)。こうしておくとコミットをスカッシュしたときに正しいエントリを生成します。 - -### 関連するマージリクエストをオーバーライドする - -GitLabは、変更履歴を生成するときに、自動的にマージリクエストをコミットにリンクします。リンクするマージリクエストをオーバーライドする場合は、`MR`トレーラーを使用して代替マージリクエストを指定できます。 - -```plaintext -Update git vendor to gitlab - -Now that we are using gitaly to compile git, the git version isn't known -from the manifest, instead we are getting the gitaly version. Update our -vendor field to be `gitlab` to avoid cve matching old versions. - -Changelog: changed -MR: https://gitlab.com/foo/bar/-/merge_requests/123 -``` - -その値は、マージリクエストのフルURLである必要があります。 - -### GitLab Enterpriseを変更する - -変更がGitLab Enterpriseエディション専用である場合は、トレーラー`EE: true`を**追加する必要**があります。 - -```plaintext -Update git vendor to gitlab - -Now that we are using gitaly to compile git, the git version isn't known -from the manifest, instead we are getting the gitaly version. Update our -vendor field to be `gitlab` to avoid cve matching old versions. - -Changelog: changed -MR: https://gitlab.com/foo/bar/-/merge_requests/123 -EE: true -``` - -EEとCEの両方に適用する変更については、トレーラーを追加**しない**でください。 - -## 変更履歴エントリが必要な場合 - -- データベース移行が行われる変更では、定期的な移行であれデプロイ後の移行であれデータ移行であれ、変更履歴エントリが無効な機能フラグの背後にあっても、変更履歴エントリが**必要**です。 -- [セキュリティ修正](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/engineer.md)には、`security`に設定された`Changelog`トレーラーを含む変更履歴エントリが**必要**です。 -- ユーザーに影響する変更には、すべて変更履歴エントリが**必要**です。例:「GitLabでは、すべてのテキストにシステムフォントを使用するようになりました。」 -- RESTやGraphQL APIへのクライアントに影響する変更には、すべて変更履歴エントリが**必要**です。[GraphQLの互換性を維持しない変更を構成する完全なリスト](api_graphql_styleguide.md#breaking-changes)を参照してください。 -- [高度な検索移行](search/advanced_search_migration_styleguide.md#create-a-new-advanced-search-migration)を行う変更には、すべて変更履歴エントリが**必要**です。 -- （月次リリースの候補版で行ったバグの修正など）同じリリースで発生してデバッグしたリグレッションの修正には、変更履歴エントリを行っては**なりません**。 -- （リファクタリング、技術的負債の修正、Testスイートの変更など）デベロッパーに影響する変更には、一切変更履歴エントリを行っては**なりません**。例:「サイクル分析モデル仕様で作成したデータベースレコードを削減します。」 -- コミュニティメンバーからの_なんらかの_コントリビュートはたとえ小さくても、コントリビューターが希望するなら、ガイドラインに関係なく変更履歴エントリを行っても**かまいません**。 -- [実験](experiment_guide/_index.md)の変更には、変更履歴エントリを行っては**なりません**。 -- ドキュメントの変更のみを含むMR（マージリクエスト）には、変更履歴エントリを行っては**なりません**。 - -詳細については、[機能フラグで変更履歴エントリを処理する方法](feature_flags/_index.md#changelog)を参照してください。 - -## 優れた変更履歴エントリを作成する - -優れた変更履歴エントリは、説明的で簡潔でなければなりません。これは変更に関する_背景状況をまったく知らない_読者に、変更内容を説明するものです。簡潔さと説明性の両立が難しい場合は、説明を優先させてください。 - -- **悪い例: **プロジェクトの順序に移動します。 -- **良い例:**「プロジェクトへ移動」ドロップダウンリストの一番上に、ユーザーのお気に入りプロジェクトを表示します。 - -最初の例では、変更が行われた箇所、その理由、ユーザーにどのように役立つのかといった背景状況が不明です。 - -- **悪い例: **（一部のテキスト）をクリップボードにコピーします。 -- **良い例:**「クリップボードにコピー」ツールチップを更新して、コピーする内容を示すようにします。 - -これも最初の例はあいまいすぎて、背景状況が分かりません。 - -- **悪い例: **ミニパイプライングラフのCSSとHTMLの問題を修正し改善し、ドロップダウンリストをビルドします。 -- **良い例:**ミニパイプライングラフのツールチップとホバー状態を修正し、ドロップダウンリストをビルドします。 - -最初の例は、実装の詳細に焦点を当てすぎています。ユーザーは、CSSやHTMLの変更は気にせず、その変更の_最終結果_を気にします。 - -- **悪い例: **`find_commits_by_message_with_elastic`から返されるコミットオブジェクトの配列で`nil`を取り除きます -- **良い例: **ガベージコレクションしたコミットを参照するElasticsearchの結果により、500のエラーを修正します - -最初の例は、_何_を修正したのかではなく、_どのように_修正したかに焦点を当てています。書き換えられたバージョンでは、ユーザーにとっての_最終的なメリット_（500のエラーを削減）と、_いつ_（Elasticsearchでコミットを検索したとき）を明確に説明しています。 - -最善の判断を下し、列挙した変更履歴を読んでいる人の考え方を理解するように努めてください。このエントリは価値を追加しますか？変更を行った_場所_と_理由_についての背景状況を提供していますか？ - -## 変更履歴エントリの生成方法 - -Gitトレーラーは、変更をコミットするときに追加します。これは選択したテキストエディタで実行できます。既存のコミットにトレーラーを追加するには、（最新のコミットである場合）コミットへの修正、または`git rebase -i`によるインタラクティブなリベースが必要です。 - -最終のコミットを更新するには、次の命令を実行します。 - -```shell -git commit --amend -``` - -これでコミットメッセージに`Changelog`トレーラーを追加できます。以前のコミットをremoteブランチにすでにプッシュしていた場合は、以下のように新しいコミットを強制的にプッシュする必要があります。 - -```shell -git push -f origin your-branch-name -``` - -古い（または複数の）コミットを編集するには`git rebase -i HEAD~N`を使用します。ここで`N`はリベースする最終コミット数です。たとえばブランチに3つのコミットA、B、Cがあるとします。コミットBを更新する場合は、次のコマンドを実行する必要があります。 - -```shell -git rebase -i HEAD~2 -``` - -これで最後の2つのコミットのインタラクティブなリベースセッションを開始します。開始すると、Gitは次の行に沿ってコンテンツを含むテキストエディタを表示します。 - -```plaintext -pick B Subject of commit B -pick C Subject of commit C -``` - -コミットBを更新するには、単語`pick`を`reword`に変更し、エディターを保存して終了します。いったん閉じると、Gitは新しいテキストエディタインスタンスを表示し、コミットBのコミットメッセージを編集できます。トレーラーを追加し、次にエディターを保存して終了します。すべてうまくいけば、コミットBが更新されます。 - -remoteブランチにすでに存在するコミットを変更したため、remoteブランチにプッシュするときには次のように`--force-with-lease`フラグを使用する必要があります。 - -```shell -git push origin your-branch-name --force-with-lease -``` - -インタラクティブなリベースの詳細については、[Gitドキュメント](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)を参照してください。 - ---- - -[開発ドキュメントに戻る](_index.md) diff --git a/doc-locale/ja-jp/development/chaos_endpoints.md b/doc-locale/ja-jp/development/chaos_endpoints.md new file mode 100644 index 00000000000..619d49e89ea --- /dev/null +++ b/doc-locale/ja-jp/development/chaos_endpoints.md @@ -0,0 +1,6 @@ +--- +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. +title: Generating chaos in a test GitLab instance +--- diff --git a/doc-locale/ja-jp/development/chatops_on_gitlabcom.md b/doc-locale/ja-jp/development/chatops_on_gitlabcom.md new file mode 100644 index 00000000000..d087272e2f7 --- /dev/null +++ b/doc-locale/ja-jp/development/chatops_on_gitlabcom.md @@ -0,0 +1,6 @@ +--- +stage: Deploy +group: Environments +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. +title: ChatOps on GitLab.com +--- diff --git a/doc-locale/ja-jp/development/cicd/_index.md b/doc-locale/ja-jp/development/cicd/_index.md new file mode 100644 index 00000000000..16c842f5d97 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/_index.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Execution +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. +title: CI/CD development guidelines +--- diff --git a/doc-locale/ja-jp/development/cicd/cicd_reference_documentation_guide.md b/doc-locale/ja-jp/development/cicd/cicd_reference_documentation_guide.md new file mode 100644 index 00000000000..c39a49b7ae8 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/cicd_reference_documentation_guide.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Authoring +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. +title: Documenting pipeline configuration keywords +--- diff --git a/doc-locale/ja-jp/development/cicd/cicd_tables.md b/doc-locale/ja-jp/development/cicd/cicd_tables.md new file mode 100644 index 00000000000..82cea526964 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/cicd_tables.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Execution +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. +title: Add new tables to the CI database +--- diff --git a/doc-locale/ja-jp/development/cicd/components.md b/doc-locale/ja-jp/development/cicd/components.md new file mode 100644 index 00000000000..4ee2e0c6fc0 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/components.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Authoring +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. +title: Development guide for GitLab official CI/CD components +--- diff --git a/doc-locale/ja-jp/development/cicd/configuration.md b/doc-locale/ja-jp/development/cicd/configuration.md new file mode 100644 index 00000000000..0e782e0b739 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/configuration.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Authoring +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. +title: Contribute to the CI/CD configuration +--- diff --git a/doc-locale/ja-jp/development/cicd/pipeline_wizard.md b/doc-locale/ja-jp/development/cicd/pipeline_wizard.md new file mode 100644 index 00000000000..cf9ec585cc2 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/pipeline_wizard.md @@ -0,0 +1,6 @@ +--- +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. +title: Pipeline Wizard +--- diff --git a/doc-locale/ja-jp/development/cicd/schema.md b/doc-locale/ja-jp/development/cicd/schema.md new file mode 100644 index 00000000000..9b2ab74245d --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/schema.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Authoring +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. +title: Contribute to the CI/CD Schema +--- diff --git a/doc-locale/ja-jp/development/cicd/templates.md b/doc-locale/ja-jp/development/cicd/templates.md index fb7afb0d4f9..8b193c6f678 100644 --- a/doc-locale/ja-jp/development/cicd/templates.md +++ b/doc-locale/ja-jp/development/cicd/templates.md @@ -2,381 +2,5 @@ stage: Verify group: Pipeline Authoring 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. -title: GitLab CI/CDテンプレートの作成ガイド（非推奨） +title: Development guide for GitLab CI/CD templates (Deprecated) --- - -{{< alert type="note" >}} - -GitLabは、[CI/CDカタログ](../../ci/components/_index.md#cicd-catalog)の導入により、コードベースに対する新たなCI/CDテンプレートのコントリビュートの受け付けを終了しました。それに代わるものとして、カタログ用の[CI/CDコンポーネント](../../ci/components/_index.md)をチームメンバーが作成することを推奨します。この移行に伴い、共有のCI/CDリソースのモジュール性と保守性が向上します。また、新たなCI/CDテンプレートをコントリビュートする際の複雑性を回避できます。既存のテンプレートを更新する必要がある場合は、それに対応するCI/CDコンポーネントも更新する必要があります。CI/CDテンプレートに対応するコンポーネントがまだ存在しない場合は、[対応するコンポーネントの作成](components.md)を検討してください。これを行うことで、GitLabの新しい開発プラクティスに沿って、テンプレートとコンポーネントの機能の同期を保つことができます。 - -{{< /alert >}} - -このドキュメントでは、[GitLabのCI/CDテンプレート](../../ci/examples/_index.md#cicd-templates)の作成方法について説明します。 - -## CI/CDテンプレートの要件 - -CI/CDテンプレートの新規作成または更新の際、マージリクエスト（MR）を送信する前に以下のことを行う必要があります。 - -- テンプレートを適切な[ディレクトリ](#template-directories)に配置します。 -- [CI/CDテンプレートの作成ガイドライン](#template-authoring-guidelines)に従います。 -- テンプレートの名前を`*.gitlab-ci.yml`形式に沿って設定します。 -- 有効な[`.gitlab-ci.yml`構文](../../ci/yaml/_index.md)を用います。[CI/CD lintツール](../../ci/yaml/lint.md)を使って、構文の有効性を検証します。 -- [テンプレートメトリクスを追加](#add-metrics)します。 -- マージリクエストでユーザー向けの変更が生じる場合には、[変更履歴](../changelog.md)を含めます。 -- [テンプレートレビュープロセス](#contribute-cicd-template-merge-requests)に従います。 -- （オプション、ただし強く推奨）レビュアーがアクセス可能なサンプルのGitLabプロジェクトで、テンプレートをテストします。テンプレートが必要とするデータや設定は、レビュアー自身で作成できない場合があります。サンプルのプロジェクトがあると、レビュアーがテンプレートの正確性を検証する際に役立ちます。レビュー用のマージリクエストの送信に先立ち、サンプルのプロジェクトでパイプラインを成功させておく必要があります。 - -## テンプレートディレクトリ - -テンプレートファイルはすべて`lib/gitlab/ci/templates`に保存します。一般的なテンプレートは、このディレクトリに保存します。ただし、一部の種類のテンプレートは、それぞれ専用の特定のディレクトリに保存します。[新しいファイルUIでテンプレートを選択](#make-sure-the-new-template-can-be-selected-in-ui)できるかどうかは、テンプレートのあるディレクトリによって決まります。 - -| サブディレクトリ | UIで選択可能か | テンプレートの種類 | -|----------------|------------------|---------------| -| `/*`（ルート） | 可 | 一般的なテンプレート。 | -| `/AWS/*` | 不可 | クラウドデプロイメント（AWS）関連のテンプレート。 | -| `/Jobs/*` | 不可 | Auto DevOps関連のテンプレート。 | -| `/Pages/*` | 可 | GitLab Pagesで静的サイトジェネレーターを使用するためのサンプルのテンプレート。 | -| `/Security/*` | 可 | セキュリティスキャナー関連のテンプレート。 | -| `/Terraform/*` | 不可 | Infrastructure as Code（Terraform）関連のテンプレート。 | -| `/Verify/*` | 可 | テスト機能に関連するテンプレート。 | -| `/Workflows/*` | 不可 | 「`workflow:`」キーワードを使用するためのサンプルのテンプレート。 | - -## テンプレート作成ガイドライン - -以下のガイドラインに従って、標準に準拠したテンプレートを送信するようにしてください。 - -### テンプレートの種類 - -テンプレートには2つの種類があり、それによってテンプレートの記述方法と使用方法が異なります。テンプレートの記述方式は、次の2種類のいずれかに1つに従う必要があります。 - -**パイプラインテンプレート**は、プロジェクトの構造や言語などに合わせた、エンドツーエンドのCI/CDワークフローを提供します。通常、他の`.gitlab-ci.yml`ファイルが存在しないプロジェクトで、独立して使用します。 - -パイプラインテンプレートを作成する場合: - -- `image`や`before_script`などの[グローバルキーワード](../../ci/yaml/_index.md#global-keywords)を、テンプレート上部の[`default`](../../ci/yaml/_index.md#default)セクションに配置します。 -- 既存の`.gitlab-ci.yml`ファイルで`includes`キーワードを使用してテンプレートを作成するかどうかを、[コードコメント](#explain-the-template-with-comments)で明確に指定します。 - -**ジョブテンプレート**は、既存のCI/CDワークフローに追加できる特定のジョブを提供し、特定のタスクを実行します。通常は[`includes`](../../ci/yaml/_index.md#global-keywords)キーワードを使用して、既存の`.gitlab-ci.yml`ファイルに追加して使用します。またコンテンツをコピーして既存の`.gitlab-ci.yml`ファイルに貼り付けることもできます。 - -ユーザーがほとんど、またはまったく変更せずに現在のパイプラインに追加できるよう、ジョブテンプレートを設定します。他のパイプライン設定と競合するリスクを軽減するように設定する必要があります。 - -ジョブテンプレートを作成する場合: - -- [グローバル](../../ci/yaml/_index.md#global-keywords)キーワードや[`default`](../../ci/yaml/_index.md#default)キーワードを使用しないでください。ルート`.gitlab-ci.yml`にテンプレートが含まれている場合、グローバルキーワードやデフォルトキーワードが上書きされ、予期しない動作が起こることがあります。ジョブテンプレートに特定のステージが必要な場合は、ユーザーがステージをメインの`.gitlab-ci.yml`設定に手動で追加する必要があることを、コードコメントで説明します。 -- `includes`キーワードを使用するようにテンプレートを設計しているか、既存の設定にコピーするように設計しているかを、[コードコメント](#explain-the-template-with-comments)に明記します。 -- 最新バージョンと安定バージョンでテンプレートを[バージョニング](#versioning)し、[下位互換性](#backward-compatibility)の問題の回避を検討します。このタイプのテンプレートのメンテナンスはより複雑になります。`includes`でインポートされたテンプレートの変更は、テンプレートを使用するすべてのプロジェクトのパイプラインを中断する場合があるためです。 - -テンプレートを作成する際に留意すべきその他のポイント: - -| テンプレート設計ポイント | パイプラインテンプレート | ジョブテンプレート | -|------------------------------------------------------|--------------------|---------------| -| `stages`を含むグローバルキーワードの使用 | 可 | 不可 | -| ジョブの定義 | 可 | 可 | -| 新しいファイルUI内での選択 | 可 | 不可 | -| `include`で他のジョブテンプレートを含める | 可 | 不可 | -| `include`で他のパイプラインテンプレートを含める | 不可 | 不可 | - -### 構文のガイドライン - -テンプレートをより簡単に追跡できるように、テンプレートはすべて一貫したフォーマットで、明確な構文スタイルを使用する必要があります。 - -各ジョブの`before_script`、`script`、`after_script`キーワードは [ShellCheck](https://www.shellcheck.net/)を使用してLintし、可能な限り[Shellスクリプトの標準とスタイルガイドライン](../shell_scripting_guide/_index.md)を遵守する必要があります。 - -ShellCheck は、[Bash](https://www.gnu.org/software/bash/)を使用して実行するようスクリプトを設計していることを想定しています。Bash ShellCheckルールと互換性のないシェルにスクリプトを使用するテンプレートは、ShellCheck Lintから除外できます。スクリプトを除外するには、[`scripts/lint_templates_bash.rb`](https://gitlab.com/gitlab-org/gitlab/-/tree/master/scripts/lint_templates_bash.rb)の`EXCLUDED_TEMPLATES`リストに追加します。 - -#### デフォルトブランチをハードコード化しない - -ハードコード化した`main`ブランチの代わりに[`$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH`](../../ci/variables/predefined_variables.md)を使用し、`master`は絶対に使用しないでください。 - -```yaml -job: - rules: - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH - script: - echo "example job" -``` - -#### `only`または`except`の代わりに`rules`を使用する - -可能な限り[`only`や`except`](../../ci/yaml/_index.md#only--except)の使用を避けてください。[`rules`](../../ci/yaml/_index.md#rules)が推奨構文になり、onlyやexceptはもう使用しません。 - -```yaml -job2: - script: - - echo - rules: - - if: $CI_COMMIT_BRANCH -``` - -#### 長いコマンドを分割する - -コマンドが非常に長い場合、または`-o`や`--option`のようなコマンドラインフラグが多い場合: - -- フラグを複数行のコマンドに分割して、コマンドの各部を簡単に見られるようにします。 -- フラグに長い名前が利用可能な場合は、それを使用します。 - -たとえば、`docker run --e SOURCE_CODE="$PWD" -v "$PWD":/code -v /var/run/docker.sock:/var/run/docker.sock "$CODE_QUALITY_IMAGE" /code`のような短いCLIフラグを持つ長いコマンドの場合: - -```yaml -job1: - script: - - docker run - --env SOURCE_CODE="$PWD" - --volume "$PWD":/code - --volume /var/run/docker.sock:/var/run/docker.sock - "$CODE_QUALITY_IMAGE" /code -``` - -`|`や`>`YAMLオペレータを使用して[複数行コマンドを分割](../../ci/yaml/script.md#split-long-commands)することもできます。 - -### コメントでテンプレートを説明する - -新しいファイルメニューからテンプレートの内容にアクセスできますが、それがテンプレートに関する情報をユーザーが確認できる唯一の場所である可能性があります。テンプレートの動作はテンプレート自体で明確にドキュメント化することが重要です。 - -次のガイドラインでは、すべてのテンプレート送信で想定される基本的なコメントについて説明します。コメントがユーザーや[テンプレートのレビュアー](#contribute-cicd-template-merge-requests)に役立つと思われる場合は、必要に応じてコメントを追加します。 - -#### 要件と期待値を説明する - -ファイルの先頭にある`#`コメントで、テンプレートの使用方法の詳細を提示します。これには以下が含まれます。 - -- リポジトリ/プロジェクトの要件。 -- 期待される動作。 -- テンプレートを使用する前にユーザーが編集する必要がある箇所。 -- テンプレートを設定ファイルにコピーして貼り付けるか、既存のパイプラインで`include`キーワードを用いてテンプレートを使用するか。 -- 変数をプロジェクトの CI/CD 設定に保存する必要があるか。 - -```yaml -# Use this template to publish an application that uses the ABC server. -# You can copy and paste this template into a new `.gitlab-ci.yml` file. -# You should not add this template to an existing `.gitlab-ci.yml` file by using the `include:` keyword. -# -# Requirements: -# - An ABC project with content saved in /content and tests in /test -# - A CI/CD variable named ABC-PASSWORD saved in the project CI/CD settings. The value -# should be the password used to deploy to your ABC server. -# - An ABC server configured to listen on port 12345. -# -# You must change the URL on line 123 to point to your ABC server and port. -# -# For more information, see https://gitlab.com/example/abcserver/README.md - -job1: - ... -``` - -#### 変数がテンプレートの動作にどう影響するかを説明する - -テンプレートが変数を使用する場合は、最初に定義している`#`コメントでその説明をします。変数が自明である場合は、コメントを省略できます。 - -```yaml -variables: # Good to have a comment here, for example: - TEST_CODE_PATH: # Update this variable with the relative path to your Ruby specs - -job1: - variables: - ERROR_MESSAGE: "The $TEST_CODE_PATH path is invalid" # (No need for a comment here, it's already clear) - script: - - echo ${ERROR_MESSAGE} -``` - -#### ローカル変数以外の変数には、すべて大文字の名前を使用する - -変数をCI/CD設定または`variables`キーワードを介して提供することを想定している場合、その変数には、アンダースコア（`_`）で単語を区切ったすべて大文字の名前を使用する必要があります。 - -```yaml -.with_login: - before_script: - # SECRET_TOKEN should be provided via the project settings - - echo "$SECRET_TOKEN" | docker login -u my-user --password-stdin my-registry -``` - -小文字の名前は、`script`キーワードの1つでローカルに定義している変数にオプションとして使用できます。 - -```yaml -job1: - script: - - response="$(curl "https://example.com/json")" - - message="$(echo "$response" | jq -r .message)" - - 'echo "Server responded with: $message"' -``` - -### 下位互換性 - -`include:template:`キーワードでテンプレートを動的にインクルードする場合があります。*既存*のテンプレートを変更する場合は、**絶対に**既存のプロジェクトのCI/CDを中断しないようにします。 - -たとえばテンプレート内のジョブ名を変更すると、既存のプロジェクトのパイプラインを中断する可能性があります。次のコンテンツに`Performance.gitlab-ci.yml`という名前のテンプレートがあるとします。 - -```yaml -performance: - image: registry.gitlab.com/gitlab-org/verify-tools/performance:v0.1.0 - script: ./performance-test $TARGET_URL -``` - -ユーザーは、`performance`ジョブに引数を渡してこのテンプレートを含めます。これは_ジョブ_の`.gitlab-ci.yml`でCI/CD変数`TARGET_URL`を指定すると実行できます。 - -```yaml -include: - template: Performance.gitlab-ci.yml - -performance: - variables: - TARGET_URL: https://awesome-app.com -``` - -テンプレート内のジョブ名`performance`が`browser-performance`に名前変更されたら、ユーザーの`.gitlab-ci.yml`は、インクルードされたテンプレートに`performance`という名前のジョブがなくなったため、すぐにlintエラーが発生します。よってユーザーはワークフローを煩わせる可能性のある`.gitlab-ci.yml`を修正しなければなりません。 - -破壊的変更を安全に導入するには、[バージョニング](#versioning) セクションを参照してください。 - -## バージョニング - -現在のテンプレートに依存している、既存のプロジェクトに影響を与えずに破壊的変更を導入するには、[安定](#stable-version)している[最新](#latest-version)のバージョンを使用します。 - -安定テンプレートは通常、メジャーバージョンリリースでのみ破壊的変更を受け入れますが、最新テンプレートは、どのリリースの破壊的変更でも受け入れることができます。メジャーリリースのマイルストーンでは、最新テンプレートが新しい安定テンプレートになります（最新テンプレートは削除される可能性があります）。 - -最新テンプレートの追加は安全ですが、メンテナンスの負担を伴います。 - -- GitLabは、GitLabの次のメジャーリリース時に最新テンプレートの内容で安定テンプレートを上書きする、DRIを選択する必要があります。DRIは変更に問題があるユーザーをサポートする責任を負います。 -- 新たに非破壊的変更を加える場合は、可能な限り、安定テンプレートと最新テンプレートの両方を一致させるように更新する必要があります。 -- 多くのユーザーが最新テンプレートの存在継続に直接的に依存している可能性があるため、最新テンプレートは想定よりも長く残ることがあります。 - -新たな最新テンプレートを追加する前に、変更が破壊的変更であっても、代わりに安定テンプレートに変更を加えることができるかを確認します。テンプレートがコピーペーストの使用のみを意図しているなら、安定バージョンを直接変更できる可能性があります。マイナーマイルストーンで安定テンプレートに破壊的変更を行う前に、以下を確認します。 - -- これは[パイプラインテンプレート](#template-types)であり、`includes`を使用するようには設計していないことを説明する[コードコメント](#explain-requirements-and-expectations)があること。 -- [CI/CDテンプレート使用状況メトリクス](#add-metrics)に使用状況を表示しないこと。メトリクスがテンプレートの使用状況をゼロと表示する場合、テンプレートで`include`を積極的に使用していないこと。 - -### 安定バージョン - -安定したCI/CDテンプレートは、メジャーリリースマイルストーンでのみ破壊的変更を導入するテンプレートです。テンプレートの安定バージョンには`.gitlab-ci.yml`のような名前を付けます。たとえば`Jobs/Deploy.gitlab-ci.yml`などです。 - -`15.0`のようなGitLabのメジャーマイルストーンリリースで利用できる[最新テンプレート](#latest-version)をコピーして、新しい安定テンプレートを作成できます。すべての破壊的変更は、[バージョンごとの非推奨と削除](../../update/deprecations.md)ページで告知する必要があります。 - -次の場合、`15.1`のようなマイナーGitLabリリースで安定テンプレートバージョンを変更できます。 - -- 変更が[破壊的変更](#backward-compatibility)ではないこと。 -- 変更を[最新のテンプレート](#latest-version)（存在する場合）に移植すること。 - -### 最新バージョン - -`latest`とマークしたテンプレートは、[破壊的変更](#backward-compatibility)を加える場合でも、任意のリリースで更新できます。最新バージョンと見なされる場合は、テンプレート名に`.latest`を追加します（たとえば`Jobs/Deploy.latest.gitlab-ci.yml`）。 - -[破壊的変更](#backward-compatibility)を導入する場合は、**必ず**[アップグレードパス](#verify-breaking-changes)をテストしてドキュメント化してください。通常、予期しない問題でユーザーを驚かせる可能性があるため、最新テンプレートを最適なオプションとして推奨しないでください。 - -`latest`テンプレートがまだ存在しない場合、[安定テンプレート](#stable-version)をコピーできます。 - -### 以前の安定テンプレートを含める方法 - -ユーザーは、現在のGitLabパッケージにバンドルされていない、以前の[安定テンプレート](#stable-version)を使用することがあります。たとえばGitLab 15.0とGitLab 16.0の安定テンプレートは非常に異なっているかもしれず、その場合ユーザーはGitLab 16.0にアップグレードした後でもGitLab 15.0テンプレートを引き続き使用したいと考えます。 - -`include:remote`を使用して以前のテンプレートバージョンを含める方法を説明するメモをテンプレートまたはドキュメントに追加できます。他のテンプレートを`include: template`でインクルードする場合は、`include: remote`と組み合わせることができます。 - -```yaml -# To use the v13 stable template, which is not included in v14, fetch the specific -# template from the remote template repository with the `include:remote:` keyword. -# If you fetch from the GitLab canonical project, use the following URL format: -# https://gitlab.com/gitlab-org/gitlab/-/raw//lib/gitlab/ci/templates/ -include: - - template: Auto-DevOps.gitlab-ci.yml - - remote: https://gitlab.com/gitlab-org/gitlab/-/raw/v13.0.1-ee/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml -``` - -### さらに詳しく - -GitLab CI/CDテンプレートにバージョニングの概念を導入することには、[未解決のイシュー](https://gitlab.com/gitlab-org/gitlab/-/issues/17716)があります。そのイシューを確認して、経過を見守ります。 - -## テスト - -各CI/CDテンプレートはテストして、公開しても安全であることを確認する必要があります。 - -### 手動QA - -最小限のデモプロジェクトでテンプレートをテストすることを強く推奨します。これを行うには、次の手順に従います。 - -1. に公開サンプルプロジェクトを作成します。 -1. 推奨テンプレートを使用し、`.gitlab-ci.yml`をプロジェクトに追加します。 -1. パイプラインを実行し、起こり得るすべての事例（マージリクエストパイプライン、スケジュールなど）で、すべてが適切に実行されることを確認します。 -1. 新しいテンプレートを追加するマージリクエストの説明で、プロジェクトにリンクします。 - -これはレビュアーがテンプレートを安全にマージできることを確認する際に役立つ情報です。 - -### 新しいテンプレートがUIで選択できることを確認する - -一部のディレクトリにあるテンプレートは、[**新しいファイル**UI](#template-directories)でも選択できます。いずれかのディレクトリにテンプレートを追加する場合は、ドロップダウンリストに正しく表示されることを確認します。 - -![CI/CDテンプレートの選択](img/ci_template_selection_v13_1.png) - -### RSpecテストを作成する - -パイプラインジョブが正しく生成されることを確認するには、RSpecテストを作成する必要があります。 - -1. `spec/lib/gitlab/ci/templates//_spec.rb`にテストファイルを追加します -1. `Ci::CreatePipelineService`を介してパイプラインジョブが適切に作成されるかテストします。 - -### 破壊的変更を確認する - -[`latest`テンプレート](#latest-version)に破壊的変更を導入する場合は、以下を行う必要があります。 - -1. [安定テンプレート](#stable-version)からのアップグレードパスをテストします。 -1. ユーザーがどのような種類のエラーに遭遇するかを確認します。 -1. トラブルシューティングガイドとしてドキュメント化します。 - -この情報は、メジャーバージョンのGitLabリリースで[安定テンプレート](#stable-version)を更新した場合に、ユーザーにとって重要となります。 - -### メトリクスを追加する - -すべてのCI/CDテンプレートには、その使用状況を追跡するよう定義したメトリクスも必要です。CI/CDテンプレートの月間使用状況レポートは、[Sisense（GitLab チームメンバーのみ）](https://app.periscopedata.com/app/gitlab/785953/Pipeline-Authoring-Dashboard?widget=13440051&udv=0)で確認できます。テンプレートを選択して、その単一のテンプレートのグラフを表示します。 - -新しいテンプレートのメトリクス定義を追加するには、次の手順を実行します。 - -1. [GitLab GDK](https://gitlab.com/gitlab-org/gitlab-development-kit#installation)をインストールして起動します。 -1. GDKの`gitlab`ディレクトリで、新しいテンプレートを含むブランチをチェックアウトします。 -1. 新しいテンプレートイベント名を、毎週および毎月のCI/CDテンプレートの合計数メトリクスに追加します。 - - [`config/metrics/counts_7d/20210216184557_ci_templates_total_unique_counts_weekly.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_7d/20210216184557_ci_templates_total_unique_counts_weekly.yml) - - [`config/metrics/counts_28d/20210216184559_ci_templates_total_unique_counts_monthly.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216184559_ci_templates_total_unique_counts_monthly.yml) - -1. [新しいメトリクス定義を追加](../internal_analytics/metrics/metrics_instrumentation.md#create-a-new-metric-instrumentation-class)するには、上記のイベント名と同じ名前を次のコマンドの最後の引数にします。 - - ```shell - bundle exec rails generate gitlab:usage_metric_definition:redis_hll ci_templates - ``` - - 出力は次のようになります。 - - ```shell - $ bundle exec rails generate gitlab:usage_metric_definition:redis_hll ci_templates p_ci_templates_my_template_name - create config/metrics/counts_7d/20220120073740_p_ci_templates_my_template_name_weekly.yml - create config/metrics/counts_28d/20220120073746_p_ci_templates_my_template_name_monthly.yml - ``` - -1. 新しく生成された両方のファイルを次のように編集します。 - - - `name:`と`performance_indicator_type:`: 削除します（不要）。 - - `introduced_by_url:`: テンプレートを追加するMRのURL。 - - `data_source:`: `redis_hll`に設定します。 - - `description`: このメトリクスが何を計測するのか簡単な説明を追加します。例: `Count of pipelines using the latest Auto Deploy template` - - `product_*`: [セクション、ステージ、グループ、機能カテゴリ](https://handbook.gitlab.com/handbook/product/categories/#devops-stages)を、[メトリクスディクショナリガイド](../internal_analytics/metrics/metrics_dictionary.md#metrics-definition-and-validation)に従って設定します。こういったキーワードに何を使用すべきかわからない場合は、マージリクエストでヘルプを求めることができます。 - - 各ファイルの末尾に以下を追加します。 - - ```yaml - options: - events: - - p_ci_templates_my_template_name - ``` - -1. 変更をコミットしてプッシュします。 - -たとえば、これらは[5つの詳細な本番環境アプリテンプレート](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/5-Minute-Production-App.gitlab-ci.yml)のメトリクス設定ファイルです。 - -- 毎週および毎月のメトリクス定義: - - [`config/metrics/counts_7d/20210901223501_p_ci_templates_5_minute_production_app_weekly.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/1a6eceff3914f240864b2ca15ae2dc076ea67bf6/config/metrics/counts_7d/20210216184515_p_ci_templates_5_min_production_app_weekly.yml) - - [`config/metrics/counts_28d/20210901223505_p_ci_templates_5_minute_production_app_monthly.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/metrics/counts_28d/20210216184517_p_ci_templates_5_min_production_app_monthly.yml) -- メトリクスのカウント総数: - - [`config/metrics/counts_7d/20210216184557_ci_templates_total_unique_counts_weekly.yml#L19`](https://gitlab.com/gitlab-org/gitlab/-/blob/4e01ef2b094763943348655ef77008aba7a052ae/config/metrics/counts_7d/20210216184557_ci_templates_total_unique_counts_weekly.yml#L19) - - [`config/metrics/counts_28d/20210216184559_ci_templates_total_unique_counts_monthly.yml#L19`](https://gitlab.com/gitlab-org/gitlab/-/blob/4e01ef2b094763943348655ef77008aba7a052ae/config/metrics/counts_28d/20210216184559_ci_templates_total_unique_counts_monthly.yml#L19) - -## セキュリティ - -テンプレートには、悪意のあるコードが含まれている可能性があります。たとえばジョブに`export`シェルコマンドを含むテンプレートは、ジョブログでシークレットプロジェクトのCI/CD変数を誤って公開する可能性があります。安全かどうか不明な場合は、セキュリティの専門家にクロス検証を依頼する必要があります。 - -## CI/CDテンプレートのマージリクエストにコントリビュートする - -CI/CDテンプレートのMRを作成して`ci::templates`をラベル付けしたら、DangerBotがコードをレビューできる1人のレビュアーと1人のメンテナーを提案します。マージリクエストのレビューの準備ができたら、レビュアーに[メンション](../../user/discussions/_index.md#mentions)し、CI/CDテンプレートの変更のレビューを依頼します。[CI/CD テンプレートMRのDangerBotタスク](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/44688)を追加した、マージリクエストの詳細を参照してください。 diff --git a/doc-locale/ja-jp/development/cicd/testing.md b/doc-locale/ja-jp/development/cicd/testing.md new file mode 100644 index 00000000000..f767d445892 --- /dev/null +++ b/doc-locale/ja-jp/development/cicd/testing.md @@ -0,0 +1,6 @@ +--- +stage: Verify +group: Pipeline Authoring +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. +title: Testing guide for CI/CD Rails application code +--- diff --git a/doc-locale/ja-jp/development/cloud_connector/_index.md b/doc-locale/ja-jp/development/cloud_connector/_index.md new file mode 100644 index 00000000000..b1fbb16c7f3 --- /dev/null +++ b/doc-locale/ja-jp/development/cloud_connector/_index.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Cloud Connector +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. +title: Cloud Connector +--- diff --git a/doc-locale/ja-jp/development/cloud_connector/architecture.md b/doc-locale/ja-jp/development/cloud_connector/architecture.md new file mode 100644 index 00000000000..a8549f8b78f --- /dev/null +++ b/doc-locale/ja-jp/development/cloud_connector/architecture.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Cloud Connector +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. +title: 'Cloud Connector: Architecture' +--- diff --git a/doc-locale/ja-jp/development/cloud_connector/configuration.md b/doc-locale/ja-jp/development/cloud_connector/configuration.md new file mode 100644 index 00000000000..a5311eb1bec --- /dev/null +++ b/doc-locale/ja-jp/development/cloud_connector/configuration.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Cloud Connector +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. +title: 'Cloud Connector: Configuration' +--- diff --git a/doc-locale/ja-jp/development/code_comments.md b/doc-locale/ja-jp/development/code_comments.md new file mode 100644 index 00000000000..ffa40a120ac --- /dev/null +++ b/doc-locale/ja-jp/development/code_comments.md @@ -0,0 +1,6 @@ +--- +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. +title: Code comments +--- diff --git a/doc-locale/ja-jp/development/code_intelligence/_index.md b/doc-locale/ja-jp/development/code_intelligence/_index.md new file mode 100644 index 00000000000..fc5e8ff1ffe --- /dev/null +++ b/doc-locale/ja-jp/development/code_intelligence/_index.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +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: Developer documentation for the Code Intelligence feature. +title: Code intelligence development guidelines +--- diff --git a/doc-locale/ja-jp/development/code_owners/_index.md b/doc-locale/ja-jp/development/code_owners/_index.md new file mode 100644 index 00000000000..a10154869d6 --- /dev/null +++ b/doc-locale/ja-jp/development/code_owners/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Code Owners development guidelines +--- diff --git a/doc-locale/ja-jp/development/code_review.md b/doc-locale/ja-jp/development/code_review.md index 2e9ed0d1c89..b171d18c048 100644 --- a/doc-locale/ja-jp/development/code_review.md +++ b/doc-locale/ja-jp/development/code_review.md @@ -2,623 +2,5 @@ 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. -title: コードレビューガイドライン +title: Code Review Guidelines --- - -このガイドでは、コードレビューの実施と、コードレビューを受ける上でのアドバイスとベストプラクティスを紹介します。 - -GitLab CEとEEのマージリクエストはどれも、GitLabチームメンバーが作成したか、広範なコミュニティメンバーが作成したかにかかわらず、コードレビュー処理を行い、コードが効果的で、理解しやすく、保守しやすく、安全であることを確認する必要があります。 - -## マージリクエストのレビュー、承認、マージの実施 - -開始前に: - -- [コントリビュートの承認基準](contributing/merge_request_workflow.md#contribution-acceptance-criteria)をよく理解します。 -- ガイダンスが必要な場合（たとえば初めてのマージリクエストの場合）は、[マージリクエストコーチ](https://about.gitlab.com/company/team/?department=merge-request-coach)の1人にお気軽にお問い合わせください。 - -レビューするコードができたらすぐに、[レビュアー](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#reviewer)のコード**レビュー**を受けます。このレビュアーは、グループやチームのメンバー、または[特定領域のエキスパート](#domain-experts)である場合があります。レビュアーは以下を行います。 - -- 選択したソリューションと実装について、セカンドオピニオンを提供します。 -- バグ、ロジックの問題、または未解決のエッジケースを探す支援をします。 - -マージリクエストが小規模でレビューが簡単な場合は、レビュアーのステップをスキップして、直接[メンテナー](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#maintainer)に依頼できます。 - -何が「小規模で簡単」であるかはグレーゾーンです。小規模で簡単な変更の例を次に示します。 - -- タイプミスを修正したり、コピーを少し変更したりする場合（[例](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/121337#note_1399406719)）。 -- 動作やデータを変更しない、ごくわずかなリファクタリング。 -- 1か月以上デフォルトで有効になっている機能フラグへの参照の削除。 -- 未使用のメソッドやクラスの削除。 -- コードの5行未満の変更を必要とする、よく理解されているロジックの変更。 - -それ以外の場合、マージリクエスト（MR）は、MRが影響を与える各[カテゴリ（バックエンド、データベースなど）](#approval-guidelines)のレビュアーによる最初のレビューを受ける必要があります。なぜならメンテナーは関連する特定領域の知識を持っていない可能性があるためです。これはワークロードの分散にも役立ちます。 - -セキュリティスキャンやコメントの支援については、アプリケーションセキュリティチーム（`@gitlab-com/gl-security/appsec`）を含めます。 - -レビュアーは、サイドバーの[レビュアー機能](../user/project/merge_requests/reviews/_index.md)を使用します。レビュアーは、[追加で承認](../user/project/merge_requests/approvals/_index.md#approve-a-merge-request)して承認を追加できます。 - -マージリクエストが影響を与える領域に応じて、1人以上の[メンテナー](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#maintainer)による**承認**が必要となります。**承認**ボタンは、マージリクエストウィジェットにあります。 - -マージリクエストを**マージ**するには、メンテナーも必要です。複数の承認が必要な場合、レビューし承認する最後のメンテナーがマージします。 - -一部の特定領域（`Verify`など）では、CODEOWNERSルールに基づいて、特定領域エキスパートの承認が必要です。CODEOWNERSセクションは独立した承認ルールであるため、他のより一般的な承認ルール（`backend`など）のサブセットである、特定のルール（`Verify`など）が存在する可能性があります。より効率的に処理するには、作成者が一般的な承認の前に特定領域固有の承認を求める必要があります。特定領域固有の承認者はメンテナーでもある可能性があり、その場合は特定領域固有の変更と、より広範な変更を同時にレビューし、両方のロールに対して1回承認することとします。 - -詳細は以下の[作成者の責任](#the-responsibility-of-the-merge-request-author)をお読みください。 - -### 特定領域エキスパート - -特定領域エキスパートは、特定の技術、製品機能、またはコードベースの領域で豊富な経験を持つチームメンバーです。チームメンバーは、特定領域エキスパートとしてのアイデンティティを持ち、それを[チームプロファイル](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#how-to-self-identify-as-a-domain-expert)に追加することを推奨します。 - -特定領域エキスパートとしてアイデンティティを持つ場合は、`.yml`ファイルを変更するMRを、すでに確立されている特定領域エキスパートまたは該当するエンジニアリングマネージャーがマージするように割り当てることを推奨します。 - -次のような場合には、自動的に特定領域エキスパートと見なすと想定しています。 - -- 特定のステージ/グループ（ソースコードの作成など）で作業しているチームメンバーは、作業しているアプリの領域の特定領域エキスパートと見なします。 -- 特定の機能（検索など）に取り組んでいるチームメンバーは、その機能の特定領域エキスパートと見なします。 - -コードレビューについては自動的に、特定領域の専門知識を持つチームメンバーにレビューを割り当てます。UXレビューは自動的に、レビュールーレット（ランダム選択）で推奨されたレビュアーに割り当てます。デザイナーのキャパシティの制限により、製品デザイナーがサポートしていない領域では、コミュニティへのコントリビュートでない限り、UXレビューは不要になります。適切な[特定領域エキスパート](#domain-experts)を割り当てられない場合は、チームメンバーの誰かを選択してMRをレビューするか、[レビュアールーレット](#reviewer-roulette)（ランダム選択）の推奨に従います（UXレビューについては上記を参照）。割り当てる前に、その人が不在でないか再確認します。 - -特定領域エキスパートは次の手順で見つけます。 - -- マージリクエスト承認ウィジェットで、[適格な承認者を表示](../user/project/merge_requests/approvals/rules.md#eligible-approvers)を選択します。このウィジェットは、コードベースの領域ごとに推奨される承認と必要な承認を表示します。そのルールは[コードオーナー](../user/project/merge_requests/approvals/rules.md#code-owners-as-eligible-approvers)で定義しています。 -- マージリクエストに関連する[ステージやグループ](https://handbook.gitlab.com/handbook/product/categories/#devops-stages)で作業するチームメンバーのリストを表示します。 -- [エンジニアリングプロジェクト](https://handbook.gitlab.com/handbook/engineering/projects/)ページまたは[GitLabチームページ](https://about.gitlab.com/company/team/)に、チームメンバーの特定領域での専門知識を表示します。特定領域は自分で識別するため、自分の判断でマージリクエストの変更を特定領域にマッピングします。 -- マージリクエストの対象ファイルに貢献したチームメンバーを探します。`git log `を実行してログを表示します。 -- ファイルをレビューしたチームメンバーを探します。関連するマージリクエストは、次の方法で見つけます。 - 1. `git log `を使用して、コミットSHAを取得します。 - 1. `https://gitlab.com/gitlab-org/gitlab/-/commit/`に移動します。 - 1. コミットに表示される、関連するマージリクエストを選択します。 - -### レビュアールーレット - -{{< alert type="note" >}} - -レビュアールーレットは、GitLab.comで使用するための社内ツールであり、お客様のインストール環境では使用できません。 - -{{< /alert >}} - -[Dangerボット](dangerbot.md)は、マージリクエストが影響を与えると思われるコードベースの各領域に対して、レビュアーとメンテナーをランダムに選択します。そうしてボットがデベロッパーのレビュアーを**推奨**します。他の人がより適していると思う場合は、推奨を上書きする必要があります。 - -[承認ガイドライン](#approval-guidelines)は、[特定領域エキスパート](#domain-experts)の選択に役立ちます。 - -製品デザイナーを含むチームからのMRにのみ、UXレビューを実施します。そのようなチームからのユーザー向け変更には、機能フラグの背後にある場合でも、UXレビューが必要です。基本的には、推奨される人をUXレビュアーとします。 - -レビュアーとメンテナーは、[エンジニアリングプロジェクト](https://handbook.gitlab.com/handbook/engineering/projects/)ページのリストから、以下の条件で選択します。 - -- Slackまたは[GitLabステータス](../user/profile/_index.md#set-your-status)が次のいずれかのユーザーは、選択肢から外します。 - - 文字列`OOO`、`PTO`、`Parental Leave`、`Friends and Family`、または`Conference`が含まれている。 - - 絵文字が次のカテゴリのいずれかである。 - - **休暇中** \- 🌴 `palm_tree`、🏖️ `beach`、⛱ `beach_umbrella`、🏖 `beach_with_umbrella`、🌞 `sun_with_face`、🎡 `ferris_wheel`、🏙 `cityscape` - - **病欠** \- 🌡️ `thermometer`、🤒 `face_with_thermometer` - - 重要: ステータスの絵文字は、フリーテキスト入力の**ステータスメッセージ**に表示されている場合は検出されません。テキスト入力の横にある絵文字セレクターをクリックして、GitLabの**ステータス絵文字**で設定する必要があります。 -- 選択した「レビュー制限」以上の数のレビューがすでに割り当てられている人は選択肢から外します。レビュー制限とは、人が一度に処理できるレビューの最大数です。Slackまたは[GitLabステータス](../user/profile/_index.md#set-your-status)として次のいずれかを使用して、レビュー制限を設定します。 - - 2️⃣ - `two` - - 3️⃣ - `three` - - 4️⃣ - `four` - - 5️⃣ - `five` - - 最小レビュー制限は2️⃣です。レビューをを完全にオフにできない理由は、[このイシュー](https://gitlab.com/gitlab-org/quality/engineering-productivity/team/-/issues/377)で議論しています。 - - [セキュリティグループ](https://gitlab.com/gitlab-org/security/)下の、プロジェクトのデフォルトブランチをターゲットとしないマージリクエストのレビューリクエストは、カウントしません。このようなMRは通常はバックポートで、メンテナーやレビュアーは通常、レビューに多くの時間を費やす必要がないからです。 - -- ポイント1で示すようにオフィス不在（`OOO`）ステータスが変わらない限り、同じブランチ名には常に同じレビュアーとメンテナーを選択します。また先頭の`ce-`と`ee-`、末尾の`-ce`と`-ee`を削除し、バックポートブランチが安定するようにします。 -- Slackまたは[GitLabステータス](../user/profile/_index.md#set-your-status)の絵文字がⓂ `:m:`の人は、メンテナーであるプロジェクトのレビュアーとしてのみ提案されます。 - -[ルーレットダッシュボード](https://gitlab-org.gitlab.io/gitlab-roulette/)には次のものが含まれています。 - -- 過去7日間と30日間の割り当てイベント。 -- 現在、1人あたりに割り当てられているマージリクエスト。 -- さまざまな基準による並べ替え。 -- 手動レビュアールーレット。 -- 現地時間の情報。 - -詳細については、[ルーレットのREADME](https://gitlab.com/gitlab-org/gitlab-roulette/)をレビューしてください。 - -### 承認ガイドライン - -以下のメンテナーの責任に関するセクションで説明しているように、[特定領域の専門知識](#domain-experts)を持つメンテナーにマージリクエストを承認し、マージしてもらうことを推奨します。最初のレビュアーのオプションとしての承認は、これには含まれません。ただしマージリクエストは、[概要](#getting-your-merge-request-reviewed-approved-and-merged)セクションで説明しているように、メンテナーに渡す前にレビュアーがレビューする必要があります。 - -| マージリクエストに以下が含まれている場合 | 以下の担当者による承認が必要 | -| ------------------------------- | ------------------------ | -| `~backend`の変更1 | [バックエンドメンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_backend)。 | -| `~database`の移行またはコストのかかるクエリの変更2 | [データベースメンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_database)。詳細は[データベースレビューガイドライン](database_review.md)を参照してください。 | -| `~workhorse`の変更 | [Workhorseメンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_workhorse)。 | -| `~frontend`の変更1 | [フロントエンドメンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_frontend)。 | -| `~UX`ユーザー向け変更3 | [製品デザイナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_UX)。詳細については、[設計とユーザーインターフェイスのガイドライン](contributing/design.md)を参照してください。 | -| 新しいJavaScriptライブラリの追加1 | \- ライブラリが[バンドルサイズ](https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics/-/blob/main/doc/report.md)を大幅に増やす場合は、[フロントエンドデザインシステムのメンバー](https://about.gitlab.com/direction/foundations/design_system/)。
\- 新しいライブラリで使用するライセンスが、GitLabでの使用の承認を得ていない場合は、[法務部門のメンバー](https://handbook.gitlab.com/handbook/legal/)。

ライセンスの互換性に関する詳細については、[GitLabライセンスと互換性に関するドキュメント](licensing.md)を参照してください。 | -| 新しい依存関係またはファイルシステムの変更 | - [配布チームメンバー](https://about.gitlab.com/company/team/)。詳細は[配布チーム](https://handbook.gitlab.com/handbook/engineering/infrastructure/core-platform/systems/distribution/#how-to-work-with-distribution)との作業方法を参照してください。
\- RubyGemsの場合は、[AppSecレビュー](gemfile.md#request-an-appsec-review)をリクエストします。 | -| `~documentation`または`~UI text`の変更 | 適切な[DevOpsステージグループ](https://handbook.gitlab.com/handbook/product/categories/#devops-stages)の割り当てに基づく[テクニカルライター](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments)。 | -| 開発ガイドラインの変更 | [レビュープロセス](development_processes.md#development-guidelines-review)に従い、それに応じて承認を取得します。 | -| エンドツーエンドの変更**と**非エンドツーエンドの変更4 | [テスト担当ソフトウェアエンジニア](https://handbook.gitlab.com/handbook/engineering/quality/#individual-contributors)。 | -| エンドツーエンドの変更のみ4**または**MR作成者が[テスト担当ソフトウェアエンジニア](https://handbook.gitlab.com/handbook/engineering/quality/#individual-contributors)の場合 | [品質メンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_qa)。 | -| [アプリケーション制限](https://handbook.gitlab.com/handbook/product/product-processes/#introducing-application-limits)の新規作成または更新 | [製品マネージャー](https://about.gitlab.com/company/team/)。 | -| 分析機器（遠隔測定または分析）の変更 | [分析機器のエンジニア](https://gitlab.com/gitlab-org/analytics-section/analytics-instrumentation/engineers)。 | -| [機能仕様](testing_guide/testing_levels.md#frontend-feature-tests)の追加または変更 | [品質メンテナー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_qa)または[品質レビュアー](https://handbook.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_qa)。 | -| GitLabへの新しいサービス（Puma、Sidekiq、Gitalyなど） | [製品マネージャー](https://about.gitlab.com/company/team/)。詳細は、[GitLabにサービスコンポーネントを追加するプロセス](adding_service_component.md)を参照してください。 | -| 認証に関連する変更 | [管理: 認証](https://about.gitlab.com/company/team/)。詳細については、[グループページのコードレビューセクション](https://handbook.gitlab.com/handbook/engineering/development/sec/software-supply-chain-security/authentication/#code-review)を確認してください。チームによるレビューが必要なことがわかっているファイルのパターンは、[`CODEOWNERS`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/CODEOWNERS)ファイルの`Authentication`セクションにリストしており、これらのファイルを変更するすべてのマージリクエストの承認者セクションに、チームをリスト表示します。 | -| カスタムロールまたはポリシーに関連する変更 | [管理: 承認エンジニア](https://gitlab.com/gitlab-org/software-supply-chain-security/authorization/approvers/)。 | - -1. JavaScript仕様以外の仕様は、`~backend`コードと見なします。Hamlマークアップは`~frontend`コードと見なします。ただし、HamlテンプレートでのRubyコードは`~backend`コードと見なします。不明な場合は、フロントエンドとバックエンドの両方のレビューをリクエストします。 -1. マージリクエストによってコストのかかるクエリが起こる可能性がある場合は、データベースメンテナーにガイダンスを求めることを推奨します。疑問のあるコードの行にSQLクエリでコメントするのが最も効率的で、そうするとメンテナーがアドバイスできます。 -1. ユーザー向け変更には、視覚的な変更（変更の軽微さに無関係）と、スクリーンリーダーがコンテンツをアナウンスする方法に影響を与える、レンダリングしたDOMへの変更の両方が含まれます。専任の製品デザイナーがいないグループでは、変更がコミュニティへのコントリビュートでない限り、製品デザイナーが機能の変更を承認する必要はありません。 -1. エンドツーエンドの変更には、`qa`ディレクトリ内の全ファイルが含まれます。 - -#### CODEOWNERSの承認 - -一部のマージリクエストでは、特定のグループによる必須の承認が必要です。定義については`.gitlab/CODEOWNERS`を参照してください。 - -`.gitlab/CODEOWNERS`の必須セクションは、次の理由により必要な場合にのみ制限する必要があります。 - -- コンプライアンス -- 可用性 -- セキュリティ - -必須セクションを追加するときは、マージリクエストの進行度に対する新しい必須セクションの影響を追跡する必要があります。その好例については、[Verifyイシュー](https://gitlab.com/gitlab-org/gitlab/-/issues/411559)を参照してください。 - -その他のすべてのケースでは、[硬直性よりも責任](https://handbook.gitlab.com/handbook/values/#freedom-and-responsibility-over-rigidity)を優先するため、必須セクションを使用しないでください。 - -さらに一枚岩的な現在の構造は、マージリクエストが見かけ上無関係な部分に影響する可能性が高いことを意味します。複数の承認が必須であるとは、そのようなマージリクエストでは作成者が承認を求める必要があることを意味しますが、それは効率的ではありません。 - -これを改善するための取り組みは次のとおりです。 - -- -- - -#### 受け入れチェックリスト - - - -このチェックリストを使用して、マージリクエスト（MR）の作成者、レビュアー、メンテナーが、品質、パフォーマンス、信頼性、セキュリティ、可観測性、保守性に対する影響の大きいリスクについて変更を分析したことを確認してください。 - -チェックリストを使用すると、ソフトウェアエンジニアリングの品質が向上します。このチェックリストは、GitLabコードベースへのコントリビューターのスキルをサポートし、強化するための明快なツールです。 - -##### 品質 - -品質ガイドラインの詳細については、[テストエンジニアリングプロセス](https://handbook.gitlab.com/handbook/engineering/infrastructure/test-platform/test-engineering/)を参照してください。 - -1. [コードレビューガイドライン](code_review.md)に従って、このMRを自己レビューしました。 -1. コードは[ソフトウェア設計ガイドライン](software_design.md)に従っています。 -1. [テストピラミッド](testing_guide/testing_levels.md)に従って、[自動テスト](testing_guide/_index.md)の存在を確認します。不足しているテストを追加するか、テストギャップを文書化するイシューを作成します。 -1. GitLab.com、Dedicated、Self-Managedに対する技術的な影響を検討しました。 -1. 必要に応じて、システムのフロントエンド、バックエンド、データベースの一部分へのこの変更の影響を検討し、それに応じて`~ux`、`~frontend`、`~backend`、`~database`のラベルを付けました。 -1. [サポートされているすべてのブラウザ](../install/requirements.md#supported-web-browsers)でこのMRをテストしました。あるいはこのテストは不要と判断しました。 -1. この変更が[アップデート間で下位互換性がある](multi_version_compatibility.md)ことを確認しました。あるいはこの変更は該当しないと判断しました。 -1. [EEコンテンツ](ee_features.md)（存在する場合）をFOSSから適切に分離しました。[FOSSコンテキストでCIパイプラインを実行](ee_features.md#run-ci-pipelines-in-a-foss-context)することを検討します。 -1. 既存のデータが実に多様であるかもしれないことを検討しました。たとえば、新しいモデル検証を追加する場合は、既存のデータではオプションにすることを検討します。 -1. このMRに関連するFlakyテストを修正したか、または無視できる理由を説明しました。Flakyテストには`Flaky test '' was found in the list of files changed by this MR.`というエラーがありますが、警告付きでパスするジョブに存在する可能性があります。 - -##### パフォーマンス、信頼性、可用性 - -1. このMRがパフォーマンスを損なうことはないと確信しているか、あるいはレビュアーにパフォーマンスへの影響の評価のサポートを依頼しました。（[マージリクエストのパフォーマンスガイドライン](merge_request_concepts/performance.md)） -1. [MRの説明にデータベースのレビュアー向けの情報](database_review.md#required)を追加したか、不要であると判断しました。 - - [このMRにはデータベース関連の変更が含まれていますか？](database_review.md) -1. この変更による可用性と信頼性のリスクを検討しました。 -1. 将来予測される成長に基づいて、スケーラビリティのリスクを検討しました。 -1. 平均的なお客様よりも大幅に多くのデータを持つ可能性のある大規模なお客様に対する、この変更によるパフォーマンス、信頼性、可用性への影響を検討しました。 -1. [最小システム](../install/requirements.md)で GitLab を実行する可能性のあるお客様に対する、この変更によるパフォーマンス、信頼性、可用性への影響を検討しました。 - -##### 可観測性の計測機器 - -1. 観測によりデバッグとプロアクティブなパフォーマンス改善を促進する機器を十分に含めました。機能フラグ、ログの生成、機器の追加の[例](https://gitlab.com/gitlab-org/gitlab/-/issues/346124#expectations)を参照してください。 - -##### ドキュメント - -1. 変更履歴トレーラーを含めたか、または不要であると判断しました。 - - [このMRには変更履歴が必要ですか？](changelog.md#what-warrants-a-changelog-entry) -1. ドキュメントを追加/更新したか、またはこのMRではドキュメントの変更は不要であると判断しました。 - - [ドキュメントは必須ですか？](https://handbook.gitlab.com/handbook/product/ux/technical-writing/workflow/#documentation-for-a-product-change) - -##### セキュリティ - -1. このMRに認証情報やトークン、承認、認証方法、または[セキュリティレビューガイドライン](https://handbook.gitlab.com/handbook/security/product-security/application-security/appsec-reviews/#what-should-be-reviewed)に記載されているその他の項目の処理や保存に対する変更が含まれている場合、`~security`ラベルを追加し、`@`で`@gitlab-com/gl-security/appsec`にメンションしたことを確認しました。 -1. セキュリティレビューをリクエストする**時期**と**方法**について、[内部アプリケーションセキュリティレビュー](https://handbook.gitlab.com/handbook/security/product-security/application-security/appsec-reviews/#internal-application-security-reviews)に関するドキュメントをレビューし、この変更で必要であれば、セキュリティレビューをリクエストしました。 -1. [マージリクエスト承認ポリシー](https://gitlab.com/gitlab-com/gl-security/security-policies)により、MRをブロックしているセキュリティスキャン結果がある場合： - - 真陽性の結果については、マージリクエストをマージする前に修正する必要があります。この場合、マージリクエスト承認ポリシーで必要となるAppSec承認が不要となります。 - - 偽陽性の結果、リスク許容について議論する必要があるもの、または疑わしいものについては、`@gitlab-com/gl-security/appsec`にpingします。 - -##### デプロイ - -1. 変更が高リスクである可能性があるため、この変更に機能フラグを使用することを検討しました。 -1. 機能フラグを使用している場合は、本番環境でテストする前にステージングで変更のテストを計画し、すべてのお客様に展開する前に、本番環境の顧客のサブセットで運用を開始することを検討しました。 - - [機能フラグを使用する場合](https://handbook.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#when-to-use-feature-flags) -1. [完了の定義](contributing/merge_request_workflow.md#definition-of-done)に従って、デフォルト設定または新しい設定変更をインフラストラクチャ部門に通知したか、または不要であると判断しました。 - -##### コンプライアンス - -1. 正しい[MRタイプラベル](labels/_index.md)が付けられいることを確認しました。 - -### マージリクエストの作成者の責任 - -最適なソリューションを見つけて実装する責任は、マージリクエストの作成者にあります。作成者または[直接の責任者](https://handbook.gitlab.com/handbook/people-group/directly-responsible-individuals/)（DRI）は、コードレビューのライフサイクル全体を通して、マージリクエストに担当者として割り当てられたままになります。自分を担当者として設定できない場合は、[レビュアー](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#reviewer)に依頼します。 - -メンテナーからのレビューをリクエストして、承認しマージする前に、以下を確認する必要があります。 - -- 解決すべき問題をそれで実際に解決すること。 -- 最も適切な方法で解決すること。 -- すべての要件を満たしていること。 -- バグ、論理的な問題、未解決のエッジケース、または既知の脆弱性が残っていないこと。 - -これを行うための最良の方法として、またレビュアーとの不要なやり取りを避けるために、[コードレビュー](#reviewing-a-merge-request)ガイドラインに従って、自分自身のマージリクエストの自己レビューを実行します。この自己レビュー中には、決定やトレードオフが行われた行、またはコンテキストの説明によってレビュアーがコードをより簡単に理解するのに役立つ可能性がある行について、MR内にコメントを含めるようにします。 - -ソリューションに必要なレベルの信頼を得るために、作成者には、調査や実装プロセスに他の人を適宜関与させることを期待しています。 - -さまざまなソリューションについて話し合ったり、実装のレビューを受けるために[特定領域エキスパート](#domain-experts)に連絡したり、混乱の解消や最終結果が彼らが考えていたものと一致することを確認するために製品マネージャーやUXデザイナーに連絡したり、データモデルや特定のクエリに関する意見を得るためにデータベーススペシャリストに連絡したり、ソリューションの詳細なレビューを受けるために他の開発者に連絡したりすることを推奨します。 - -ある機能を達成するために多くのマージリクエストが必要になることがわかっている場合（たとえば概念実証を作成して、機能が10以上のマージリクエストで構成されることが明らかな場合）、その機能に必要な理解を持つレビュアーとメンテナーを特定し、コンテキストを彼らと共有することを検討します。次にすべてのマージリクエストをこれらのレビュアーに送信します。これらのレビュアーを見つける最適なDRIは、EMやスタッフエンジニアです。同じコンテキストの複数のマージリクエストに、安定したレビュアーという担当者を持つと、効率が向上します。 - -マージリクエストが複数の特定領域（たとえば動的な分析とGraphQL）に影響する場合は、各特定領域のエキスパートにレビューを依頼します。 - -作成者がマージリクエストに[特定領域エキスパート](#domain-experts)の意見が必要かどうかわからないのであれば、必要ということです。意見を求めなければ、ソリューションに必要なレベルの信頼性を得られる可能性は低まりす。 - -レビューの前に作成者はマージリクエストの差分の程度に関するコメントを送信して、重要なものや、さらなる説明や注意が必要なものについてレビュアーに警告するように求められます。コメントを必要とする可能性のあるコンテンツの例を次に示します。 - -- Lintルール（RuboCop、JSなど）の追加。 -- ライブラリ（Ruby gem、JS libなど）の追加。 -- 明白でない場合は、親クラスまたはメソッドへのリンク。 -- 変更を補足するために実行したベンチマーク。 -- 安全でない可能性があるコード。 - -レビュアーがソリューションを検証するにあたって必要なプロジェクト、スニペット、またはその他の資産がある場合、レビューをリクエストする前に、レビュアーがその資産へのアクセス権を持っていることを確認します。 - -レビュアーを割り当てる際には、次のような点が役立ちます。 - -- どの*タイプ*のレビューをそのレビュアーに求めているかを示すコメントをMRに追加します。 - - たとえばMRがデータベースクエリを変更し、バックエンドコードを更新する場合、MR作成者は最初に`~backend`レビューと`~database`レビューを必要とします。レビュアーを割り当てる際に作成者は、各レビュアーにどの特定領域をレビューする必要があるかを知らせるコメントをMRに追加します。 - - 多くのGitLabチームメンバーは複数の特定領域でのエキスパートであるため、このタイプのコメントがないと、どのタイプのレビューを提供するように求められているのかが曖昧になる場合があります。 - - MRレビュータイプを明確に示すと、MR作成者にとっては求めているタイプのレビューが得られるために効率的で、またMRレビュアーにとっては、どのタイプのレビューを提供するかをすぐに知ることができるため効率的です。 - - [例1](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75921#note_758161716) - - [例2](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/109500#note_1253955051) - -避けるべきこと： - -- TODOコメント（上記参照）をソースコードに直接追加すること（レビュアーが要求する場合を除く）。実行可能なタスクのためにTODOコメントを追加する場合は、[関連するイシューへのリンクを含めます](code_comments.md)。 -- コードが行っていることを説明するだけのコメントを追加すること。TODO以外のコメントを追加する場合は、[_その理由を説明すべきで、内容の説明は不要です_](https://blog.codinghorror.com/code-tells-you-how-comments-tell-you-why/)。 -- 失敗したテストを含むマージリクエストのメンテナーレビューをリクエストすること。テストが失敗し、レビューをリクエストする必要がある場合は、必ず説明を含むコメントを残してください。 -- メールやSlackを通じて過度にメンテナーにメンションすること（メンテナーがSlackを通じて連絡できる場合）。マージリクエストのレビュアーを追加できない場合は、`@`コメントでメンテナーへのメンションは許容されますが、それ以外の場合はレビュアーの追加で十分です。 - -これでレビュアーの時間を節約し、作成者がより早くミスを把握できるようになります。 - -### レビュアーの責任 - -レビュアーには、選択されたソリューションの詳細をレビューする責任があります。 - -[レビュー応答 SLO](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#review-response-slo)内で割り当てられたマージリクエストをレビューできない場合： - -1. レビューできないことを作成者に通知します。 -1. [GitLabレビューワークロードダッシュボード](https://gitlab-org.gitlab.io/gitlab-roulette/)を使用して、新しいレビュアーを選択します。 -1. マージリクエストに新しいレビュアーを割り当てます。 - -これは[迅速な行動](https://handbook.gitlab.com/handbook/values/#operate-with-a-bias-for-action)の実践で、効率的なMRレビューの進行を保証します。 - -次のようなコメントを追加します。 - -```plaintext -Hi <@mr-author>, I'm unavailable for review but I've [spun the roulette wheel](https://gitlab-org.gitlab.io/gitlab-roulette/) for this project and it has selected <@new-reviewer>. - -@new-reviewer may you please review this MR when you have time? If you're unavailable, please [spin the roulette wheel](https://gitlab-org.gitlab.io/gitlab-roulette/) again and select and assign a new reviewer, thank-you. - -/assign_reviewer <@new-reviewer> -/unassign_reviewer me -``` - -徹底的に[マージリクエストをレビュー](#reviewing-a-merge-request)します。 - -マージリクエストがすべての[コントリビュートの受入基準](contributing/merge_request_workflow.md#contribution-acceptance-criteria)を満たしていることを確認します。 - -マージリクエストによっては、特定領域エキスパートが細部を支援する必要がある場合があります。レビュアーは、その特定領域のエキスパートでない場合、次のいずれかを行うことができます。 - -- マージリクエストをレビューし、別のレビューの特定領域エキスパートに最新情報を伝えます。このエキスパートは、別のレビュアーまたはメンテナーのいずれかになります。 -- より適切と思われる別のレビュアーにレビューを渡します。 -- 特定領域エキスパートを起用できない場合は、できる範囲内で最善のレビューをします。 - -以下の場合に、マージリクエストをより小さなマージリクエストに分割するよう作成者を誘導する必要があります。 - -- 大きすぎる。 -- 複数の問題を修正する。 -- 複数の機能を実装する。 -- 複雑性が高く、追加のリスクが発生する。 - -作成者は、現在のメンテナーとレビュアーが分割したMRをレビューするようリクエストするか、新しいメンテナーとレビュアーのグループをリクエストするかを選択できます。 - -作成者がローカル検証ステップを追加した場合は通知します。それでメンテナーはその検証を行ったか、また結果がどうだったかを把握できます。 - -すべての要件を満たしていると確信した場合は、以下を実行する必要があります。 - -- **承認**を選択します。 -- `@`で作成者にメンションしてTo Do通知を生成し、マージリクエストがレビューされ承認されたことを通知します。 -- メンテナーのレビューをリクエストします。基本的には[特定領域の専門知識](#domain-experts)を持つメンテナーを選択しますが、起用できない場合、またはそのマージリクエストには[特定領域エキスパート](#domain-experts)によるレビューが不要だと思われる場合は、[レビュアールーレット](#reviewer-roulette)の推奨事項に従います。 - -### メンテナーの責任 - -メンテナーは、特定領域と製品分野全体にわたって、GitLabコードベースの全体的な健全性、品質、一貫性について責任を負います。 - -したがって彼らのレビューは主に、全体的なアーキテクチャ、コード構成、懸念点の分離、テスト、難解さ、一貫性、読みやすさなどの点に焦点を当てます。 - -メンテナーの仕事は具体的な特定領域に関する知識ではなく、GitLabコードベース全体の知識にのみ依存しているため、どのチームのどの製品分野のMRでもレビュー、承認、マージできます。 - -メンテナーは、マージリクエストの受け入れ基準が妥当に満たされていることを保証するDRIです。一般に、[品質はすべての人の責任](https://handbook.gitlab.com/handbook/engineering/quality/)ですが、MRのメンテナーは、MRがそういった一般的な品質基準を満たしていることを**確認**する責任を負います。 - -これには[フォローアップイシューでの技術的負債の発生の回避](contributing/issue_workflow.md#technical-debt-in-follow-up-issues)が含まれます。 - -メンテナーがMRに十分な価値があると感じる場合、または[特定領域エキスパート](#domain-experts)が必要な場合、メンテナーは別のレビュアーや別のメンテナーからのレビューをリクエストする裁量権を持ちます。レビュー中にメンテナーがこれをプロアクティブに行う例を次に示します。 - -- -- -- - -メンテナーは、マージする前に選択したソリューションの詳細のレビューにも最善を尽くしますが、必ずしも[特定領域エキスパート](#domain-experts)であるとは限らないため、妥当な時間的投資に見合ってそうすることが難しい場合があります。そのような場合、彼らは作成者と以前のレビュアーの判断に従い、主な責任に注力することを優先します。 - -たまたまメンテナーでもある開発者がレビュアーとしてマージリクエストに関与した場合、最終的に承認してマージするメンテナーとしても起用しないことを推奨します。 - -メンテナーはマージする前に、マージリクエストを必要な承認者が承認しているかを確認する必要があります。他からさらに承認をまだ待っている場合は、`@`で作成者にメンションし、コメントで理由を説明します。 - -特定のマージリクエストは安定したブランチをターゲットにしている可能性があります。このようなリクエストの処理方法の概要については、[パッチリリース手順書](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md)を参照してください。 - -マージ後、メンテナーはマージリクエストにリストされているレビュアーであり続ける必要があります。 - -### レビュアー機能のドッグフーディング - -当社のコードレビュープロセスは、[マージリクエストのレビュー機能](../user/project/merge_requests/reviews/_index.md)をドッグフーディングしています。概要を以下に示します。これは他のセクションにも反映します。 - -- マージリクエストの作成者とDRIは、担当者であり続けます。 -- マージリクエストのレビュアーは、レビュー後もレビュアーであり続けます。 -- 作成者は、ユーザーをレビュアーとして割り当てて、[レビューをリクエスト](../user/project/merge_requests/reviews/_index.md#request-a-review)します。 -- 作成者が変更を加えてレビュアーに再レビューを依頼する場合は、[レビューを再リクエスト](../user/project/merge_requests/reviews/_index.md#re-request-a-review)します。 -- レビュアーは、[レビュー機能](../user/project/merge_requests/reviews/_index.md#start-a-review)を使用してフィードバックを送信します。MRの任意のコメントコンテキストで、**コメントを今すぐ追加**ではなく、**レビューを開始**または**あるレビューを開始**を選択します。 - -## ベストプラクティス - -### 全員 - -- 思いやりを持ちます。 -- 多くのプログラミング判断は見解であることを受け入れます。トレードオフやどちらを好むかについて話し合い、迅速に解決策を見つけます。 -- 質問をし、要求はしません。（「この`:user_id`という名前の付け方についてどう思いますか？」） -- 明確化を求めます。（「理解できませんでした。明確にしてもらえますか？」） -- コードの所有権の選択を避けます。（「私のもの」、「私のものじゃない」、「あなたのもの」） -- 個人の特性を指すと見なされる可能性のある用語（「ばか」、「愚か」）の使用は避けます。誰もが知的で善意を持っていると想定します。 -- はっきり表現します。人はオンラインで必ずしもあなたの意図を理解しているとは限らないことを忘れないでください。 -- 謙虚でいます。（「よくわかりません。調べてみましょう。」） -- 誇張しません。（「常に」、「決して」、「際限なく」、「何もない」） -- 皮肉の使用には注意してください。私たちが行うことはすべて公開されています。あなたと長年の同僚にとって悪意のない有効的なからかいのように見えることは、プロジェクトに不慣れな人にとっては意地悪で歓迎されないように見えるかもしれません。 -- 「理解できませんでした」または「代替ソリューション: 」コメントが多すぎる場合は、1対1のチャットまたはビデオ通話を検討します。1対1のディスカッションを要約するフォローアップコメントを投稿します。 -- 特定の人物に質問する場合は、常にコメントの冒頭でその人物にメンションします。そうすると通知レベルが「メンション済み」に設定されていればその人物が確実に参照でき、他の人々は応答する必要がないことを理解します。 - -### 変更をより迅速にマージするためのMR作成者への推奨事項 - -1. ベストプラクティスに従っていることを確認します。 - - 効率的な手順を記述し、スクリーンショット、検証手順などを追加します。 - - `dangerbot`が追加したコメントを読んで対処します。 - - [受け入れチェックリスト](#acceptance-checklist)でチェックします。 -1. より良い方法があると思っても、GitLabのパターンに従います。 - - 議論はコードのマージを遅らせることがよくあります。議論が長すぎる場合は、文書化アプローチまたはメンテナーの提案に従うことを検討してから、ベストプラクティスの一部としてご自分のアプローチを実装するために別のMRを開き、そこで議論を行います。 -1. 大きなMRを小さく分割することを検討します。約`200`行が適切な目安となります。 - - 小さいMRは、作成者とレビュアーの認知負荷を軽減します。 - - レビュアーは、最初のレビューには小さいMRを選択する傾向があります（多数のファイルは嫌われることがあります）。 - - コードの特定の部分に関する議論は、コードの他の部分のマージを妨げません。 - - 小さめのMRは多くの場合単純で、最初のレビューをスキップして[メンテナーに直接送信](#getting-your-merge-request-reviewed-approved-and-merged)したり、提案されたコンピテンシーエリア（たとえばフロントエンドやバックエンド）の1つをスキップすることを検討できます。 - - モックは、後で別のMRを追加するとしても、良いアプローチになる可能性があります。モックをサーバーリクエストに置き換えれば、通常、MRを迅速にレビューできます。 - - モックデータを含むUIは、必ず[機能フラグ](feature_flags/_index.md)の背後に配置します。 - - 過剰なリベースを避けるため、共通の依存関係を最初のMRに取り込みます。 - - シーケンシャルMRの場合は、[スタックされた差分](../user/project/merge_requests/stacked_diffs.md)を使用します。 - - 従属的なMR（たとえば`A` -> `B` -> `C`）の場合、ブランチは`master`の代わりにお互いをターゲットにします。たとえば`C`が`B`を、`B`が`A`を、`A`が`master`をターゲットにします。こうすると各MRには該当する`diff`のみが含まれます。 - - ⚠️ MRの分割で注意すべきなのは、MRが**小さすぎる**とレビューの総数が増え、逆効果となる可能性があることです。 -1. 単一のMRでのレビュアー数を最小限に抑えます。 - - 例: DBレビュアーはバックエンドやテストもレビューできます。フルスタックエンジニアはフロントエンドとバックエンドの両方のレビューができます。 - - モックを使用すると最初のMRは`frontend`のみになり、後でサーバーリクエストの`backend`レビューをリクエストできます（上記の「MR の分割」を参照）。 - -### マージリクエストのレビューを受ける - -コードレビューは複数回イテレーションすることがあるプロセスで、レビュアーは初回では見落とした点を後になって見つける可能性があることに留意してください。 - -- コードの最初のレビュアーは_あなた_です。新しく作成したブランチを最初にプッシュする前に、差分全体に目をとおします。内容に矛盾はないですか？変更の全体的な目的に無関係なものが含まれていませんか？デバッグコードの削除を忘れていませんか？ -- [マージリクエストのガイドライン](contributing/merge_request_workflow.md#merge-request-guidelines-for-contributors)で概説しているように、詳細な説明を記述してください。レビュアーによっては、製品の機能やコードベースの分野に詳しくない場合があります。十分な説明は、すべてのレビュアーがリクエストを理解し、効果的にテストするのに役立ちます。 -- 変更が先に行う変更のマージに依存していることがわかっている場合は、説明にそれを記述し、[マージリクエストの依存関係](../user/project/merge_requests/dependencies.md)を設定します。 -- レビュアーの提案に感謝します。（「おっしゃるとおりです。そのように変更します。」） -- 個人への意見と受け止めないでください。レビューはコードに対して行うもので、あなたに対してではありません。 -- コードが存在する理由を説明します。（「こういう理由により、こうなっています。このクラス/ファイル/メソッド/変数の名前を変更した方がわかりやすくなりますか？」） -- 関係のない変更とリファクタリングを、将来のマージリクエスト/イシューに抽出します。 -- レビュアーの視点を理解するように努めます。 -- すべてのコメントに返信するよう努めます。 -- マージリクエストの作成者は、完全に対応したスレッドのみを解決します。未解決の返信、未解決のスレッド、提案、質問などがある場合、スレッドを残しておき、レビュアーがそれを解決する必要があります。 -- すべてのフィードバックに、マージ前にMRに取り入れる変更を推奨する必要があると想定すべきではありません。それが必要かどうか、またはフォローアップイシューを作成して問題のMRがマージされた後に将来的にフィードバックに対応する必要があるかどうかは、MR作成者とレビュアーによる判断となります。 -- 以前のフィードバック過程に基づくコミットを、別のコミットとしてブランチにプッシュします。ブランチをマージする準備ができるまで、スカッシュしないでください。以前のフィードバックに基づいて、レビュアーが個々の更新を読めるようにしておきます。 -- 別のレビュー過程の準備ができたら、レビュアーに新しいレビューをリクエストします。レビューをリクエストする機能がない場合、代わりに`@`でレビュアーをメンションします。 - -### レビューのリクエスト - -マージリクエストのレビューを受ける準備ができたら、[承認ガイドライン](#approval-guidelines)に基づいてレビュアーを選択し、[最初のレビューをリクエスト](../user/project/merge_requests/reviews/_index.md)する必要があります。 - -マージリクエストに複数のレビュー領域がある場合は、レビュアーがどの領域を、どのステージ（第1または第2）でレビューする必要があるかを指定することを推奨します。こうすると複数の領域のレビュアーとして適格なチームメンバーは、どの領域のレビューをリクエストされているかを知ることができます。たとえば、マージリクエストに`backend`と`frontend`の両方の懸念がある場合、`@john_doe can you please review ~backend?`または`@jane_doe - could you please give this MR a ~frontend maintainer review?`のようにレビュアーにメンションできます。 - -`workflow::ready for review`ラベルも使用できます。これは、マージリクエストのレビューの準備ができており、どのレビュアーもそれを選択できることを意味します。時間的なプレッシャーがない場合にのみそのラベルを使用し、マージリクエストがレビュアーに割り当てられていることを確認することを推奨します。 - -レビューを再度リクエストする場合は、レビュアーの名前の横にある[**レビューを再リクエスト**アイコン](../user/project/merge_requests/reviews/_index.md#re-request-a-review)（{{< icon name="redo" >}}）をクリックするか、`/request_review @user`クイックアクションを使用します。これでマージリクエストは、レビュアーのマージリクエストのホームページの**リクエスト済みレビュー**セクションに表示されるようになります。 - -マージリクエストが最初のレビュアーからの承認を受けたら、メンテナーに渡すことができます。基本的には[特定領域の専門知識](#domain-experts)を持つメンテナーを選択することとし、それ以外の場合は、レビュアールーレットの推奨事項に従うか、ラベル`ready for merge`を使用します。 - -場合によっては、メンテナーがレビューに対応できないことがあります。オフィスを不在にしていたり、[他の業務で忙しい](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#review-response-slo)場合などです。メンテナーの対応可能状況はプロファイルで確認できます。ルーレットで推奨されるメンテナーが対応できない場合は、そのリストから他の人を選択します。 - -それはレビューするマージリクエストの作成者の責任です。`ready for review`状態が長すぎる場合は、特定のレビュアーにレビューをリクエストすることを推奨します。 - -### レビューへのボランティア - -業務量に余裕のあるGitLabエンジニアは、[レビュー対象のマージリクエスト](https://gitlab.com/groups/gitlab-org/-/merge_requests?state=opened&label_name%5B%5D=workflow%3A%3Aready%20for%20review)のリストを定期的にチェックし、レビューしたいマージリクエストのレビュアーとして自分自身を追加できます。 - -### マージリクエストのレビュー - -変更が必要な理由（バグの修正、ユーザーエクスペリエンスの向上、既存のコードのリファクタリング）を理解します。次に、 - -- レビューを徹底的に行ない、イテレーションの回数を減らすようにします。 -- どのアイデアを優れていると感じ、どれを感じないかを伝えます。 -- 問題を解決しながら、コードを簡素化する方法を特定します。 -- 代替の実装を提案しますが、作成者がすでにそれらを検討していると想定します。（「ここでカスタムバリデーターを使用することについてどう思いますか？」） -- 作成者の視点を理解するように努めます。 -- ブランチをチェックアウトし、ローカルで変更をテストします。実行する手動テストの量を決定できます。テストによっては、自動テストを追加する機会が得られる場合があります。 -- コードの一部が理解できない場合は、_そう言います_。他の人も同様に混乱している可能性があります。 -- 提案に対処/解決するために作成者から必要なものが何かを、作成者が理解していることを確認します。 - - 意図を伝えるために、[通常のコメント形式](https://conventionalcomments.org#format)の使用を検討します。 - - 必須ではない提案の場合は（ノンブロッキング）で装飾すれば、作成者はマージリクエスト内でオプションとして解決するか、後日フォローアップすると判断できます。提案がノンブロッキングのみの場合はMRを次のステージに進め、非同期サイクルを削減します。最初のラウンドのレビュアーである場合は、レビューするようにメンテナーに渡します。最終承認メンテナーである場合は、ノンブロッキングな提案からフォローアップを生成し、マージするか、自動マージを設定します。次に作成者が、ノンブロッキングな提案を実装して自動マージをキャンセルするか、MRのマージ後にフォローアップMRを提供するか、提案を実装しないかを決定します。 - - [Chrome/Firefox アドオン](https://gitlab.com/conventionalcomments/conventional-comments-button)を使用すると、[通常のコメント](https://conventionalcomments.org/)のプレフィックスを適用できます。 -- 未解決の依存関係がないことを確認します。ブロッカーの[リンクしたイシュー](../user/project/issues/related_issues.md)をチェックします。必要に応じて作成者に確認します。未解決のMRによってブロックされている場合は、[MR依存関係](../user/project/merge_requests/dependencies.md)を設定します。 -- 行をひととおりチェックした後、「問題ありません」や「対処すべき点が少しあります」などの要約メモを投稿すると役立つ場合があります。 -- レビュー後、変更が必要かどうかを作成者に知らせます。 - -{{< alert type="warning" >}} - -**マージリクエストがフォークからのものである場合は、[コミュニティコントリビュートの追加ガイドライン](#community-contributions)も確認します。** - -{{< /alert >}} - -### マージリクエストのマージ - -マージの決定を下す前に以下を行います。 - -- マイルストーンを設定します。 -- 正しい[MRタイプラベル](labels/_index.md#type-labels)を付けていることを確認します。 -- Danger ボット、Code Quality、その他のレポートからの警告とエラーを検討します。違反に対して強力なケースを作成できない限り、マージする前にそれらを解決する必要があります。MRを失敗したジョブとマージする場合は、コメントを投稿する必要があります。 -- MRに品質関連の変更と品質関連以外の変更の両方が含まる場合、テスト担当ソフトウェアエンジニアが品質関連の変更を承認した後、ユーザー向けの変更（バックエンド、フロントエンド、またはデータベース）を担当するメンテナーがMRをマージすることとします。 - -マージするには、少なくとも1人のメンテナーがMRを承認する必要があります。MRの作成者とMRにコミットを追加する人は、MRを承認する権限がなく、MRにコントリビュートしていないメンテナーにその承認を求める必要があります。一般に、最終的な必須承認者がMRをマージします。 - -最終承認者がMRをマージしない状況としては、以下があります。 - -- 承認者が承認後に自動マージの設定を忘れた場合。 -- 承認者が自分が最終承認者であることに気付かない場合。 -- 承認者が自動マージを設定したが、GitLabが設定を解除した場合。 - -このいずれかの状況が発生した場合、MR作成者は、必要とするすべての承認を得ていて、リポジトリに対するマージ権限を持っていれば、自分のMRをマージできます。これはGitLabの[迅速な行動](https://handbook.gitlab.com/handbook/values/#bias-for-action)の価値観にも沿っています。 - -このポリシーは、GitLabの[変更管理コントロール](https://handbook.gitlab.com/handbook/security/security-and-technology-policies/change-management-policy/)のCHG-04コントロールを満たすように導入しています。 - -`gitlab-org/gitlab`でこのポリシーを実装するために、次の設定を有効にして、MRがトップレベルのCODEOWNERSメンテナーから承認を得られるようにしました。 - -- [作成者による承認を防止](../user/project/merge_requests/approvals/settings.md#prevent-approval-by-author)。 -- [コミットを追加するユーザーによる承認を防止](../user/project/merge_requests/approvals/settings.md#prevent-approvals-by-users-who-add-commits)。 -- [マージリクエストでの承認ルールの編集を防止](../user/project/merge_requests/approvals/settings.md#prevent-editing-approval-rules-in-merge-requests)。 -- [コミットがソースブランチに追加されたときにすべての承認を削除](../user/project/merge_requests/approvals/settings.md#remove-all-approvals-when-commits-are-added-to-the-source-branch)。 - -`gitlab-org/gitlab`の`CODEOWNERS`ファイルでコードオーナーを更新するには、[コードオーナー承認ハンドブックセクション](https://handbook.gitlab.com/handbook/engineering/workflow/code-review/#code-owner-approvals)で説明しているプロセスに従います。 - -ローカルでのリベースや提案の適用などの一部のアクションは、コミットの追加と同様と見なされ、既存の承認をリセットする場合があります。UIからのリベースや[`/rebase`クイックアクション](../user/project/quick_actions.md)では、承認は削除されません。 - -マージする準備ができたら: - -{{< alert type="warning" >}} - -**マージリクエストがフォークからのものである場合は、[コミュニティコントリビュートの追加ガイドライン](#community-contributions)も確認します。** - -{{< /alert >}} - -- マージリクエストに多数のコミットがある場合は、[スカッシュしてマージ](../user/project/merge_requests/squash_and_merge.md)機能の使用を検討します。コードをマージする際には、メンテナーは、作成者がすでにこのオプションを設定している場合、またはマージリクエストに乱雑なコミット履歴が明らかに含まれている場合にのみ、スカッシュ機能を使用します。それを作成者に連絡するよりも、コミットをスカッシュする方が効率的です。それ以外の場合で、MRにコミットが数個しかないならそれらをスカッシュせず、作成者の設定を尊重します。 -- マージリクエストの**パイプライン**タブに移動し、**パイプラインの実行**を選択します。次に**概要**タブで**自動マージ**を有効にします。次の情報を考慮してください。 - - **[デフォルトブランチが壊れている](https://handbook.gitlab.com/handbook/engineering/workflow/#broken-master)場合、[非常に特殊なケース](https://handbook.gitlab.com/handbook/engineering/workflow/#criteria-for-merging-during-broken-master)を除き、マージリクエストをマージしないでください**。その他のケースについては、[ハンドブックの手順](https://handbook.gitlab.com/handbook/engineering/workflow/#merging-during-broken-master)に従ってください。 - - 最新のパイプラインがマージリクエストの承認前に作成された場合は、新しいパイプラインを開始し、完全なRSpecスイートが実行されていることを確認します。マージリクエストにバックエンドの変更が含まれていない場合にのみ、この手順をスキップできます。 - - **最新の[マージ結果パイプライン](../ci/pipelines/merged_results_pipelines.md)**が作成されて**8時間（安定ブランチの場合は72時間）未満の場合**、マージリクエストはターゲットブランチに十分に近いため、新しいパイプラインを開始せずにマージできます。 -- MRを自動マージに設定したら、その後見つかったものについては、後続のリビジョンを引き継ぐ必要があります。 -- [スカッシュしてマージ](../user/project/merge_requests/squash_and_merge.md)が設定されているマージリクエストの場合、スカッシュしたコミットのデフォルトのコミットメッセージは、マージリクエストのタイトルから取得されます。マージする前に、[より有益なコミットメッセージを含むコミットを選択](../user/project/merge_requests/squash_and_merge.md)することを推奨します。 - -**マージ結果パイプライン**のおかげで、作成者はブランチを頻繁にリベースする必要がなくなりました（競合がある場合のみ）。マージ結果パイプラインがすでに`main`からの最新の変更を取り込んでいるからです。これでメンテナーは最終的なリベースを要求する必要がなくなり、代わりにMRパイプラインを開始して自動マージを設定するだけで済むため、レビュー/マージサイクルを高速化できます。このステップにより、パイプラインの作成時に最新の`main`に対してマージ結果をテストすれば、実際のマージトレイン機能に非常に近づけられます。 - -### コミュニティコントリビュート - -{{< alert type="warning" >}} - -**悪意のあるコードがないか、すべての変更を徹底的にレビューしてから、[マージ結果パイプライン](../ci/pipelines/merge_request_pipelines.md#run-pipelines-in-the-parent-project)を開始します**。 - -{{< /alert >}} - -より広範なコミュニティコントリビューターが追加したマージリクエストをレビューする場合: - -- 新しい依存関係と依存関係の更新（Ruby gemやNodeパッケージなど）に特に注意します。`Gemfile.lock`や`yarn.lock`などのファイルへの変更は軽微に見えるかもしれませんが、悪意のあるパッケージのフェッチにつながる可能性があります。 -- リンクと画像を（特にドキュメントのMRでは）確認します。 -- 疑わしい場合は、`@gitlab-com/gl-security/appsec`の誰かに**マージリクエストパイプラインを手動で開始する前に**マージリクエストを確認するように依頼します。 -- マージリクエストが現在のマイルストーンに含まれる可能性が高い場合にのみ、マイルストーンを設定します。これはいつマージされるかについての混乱を避け、まだ準備ができていない場合にマイルストーンを頻繁に移動することを避けるためです。 - -#### コミュニティマージリクエストの引き継ぎ - -MRでさらに変更が必要な場合でも、作成者が長期間応答しない場合や、MRを完了できない場合、GitLabが引き継げます。GitLabエンジニア（通常はマージリクエストのコーチ）は以下を行います。 - -1. MRにコメントを追加して、マージできるように引き継ぐことを伝えます。 -1. MRにラベル`~"coach will finish"`を追加します。 -1. mainブランチから新しいフィーチャーブランチを作成します。 -1. ブランチを新しいフィーチャーブランチにマージします。 -1. 新しいマージリクエストを開き、フィーチャーブランチをmainブランチにマージします。 -1. MRからコミュニティMRにリンクし、`~"Community contribution"`とラベルを付けます。 -1. 必要な最終調整を行い、コントリビューターにpingして変更をレビューする機会を与え、コンテンツがmainブランチにマージされていることを通知します。 -1. コンテンツがすべてのマージリクエストガイドラインに準拠していることを確認します。 -1. 通常のマージリクエストと同様に、標準のレビュープロセスに従います。 - -### 適切なバランス - -コードレビュー中に最も難しいことの1つは、作成者が作成したコードに、レビュアーがどの程度深く介入できるかという、適切なバランスを見つけることです。 - -- 適切なバランスを見つける方法を学ぶには時間がかかります。そのため、マージリクエストのレビューに一定期間費やした後、メンテナーになるレビュアーがいます。 -- バグを見つけることは重要ですが、優れた設計について考えることも同様に重要です。抽象化と優れた設計の構築によって、複雑さを隠し、将来の変更が容易に行えるようになります。 -- [コードスタイル](contributing/style_guides.md)の順守と改善は、レビューコメントではなく、主に[自動化](https://handbook.gitlab.com/handbook/values/#cleanup-over-sign-off)を通じて行う必要があります。 -- 作成者への設計変更の依頼は、コントリビュートされたコードの完全な書き換えを意味する場合があります。それを行う前に別のメンテナーやレビュアーに相談することをお勧めしますが、それが重要であると信じる場合は、実行する勇気を持ってください。 -- [イテレーション](https://handbook.gitlab.com/handbook/values/#iteration)の利点ために、レビューでの提案がノンブロッキングな変更、または個人的な好みである（文書化または合意された要件ではない）場合は、作成者に返す前にマージリクエストの承認を検討します。こうすると作成者は自身が同意すればその提案を実装でき、メンテナーにすぐにレビューを依頼できます。これはマージまでの全体的な時間の短縮に役立ちます。 -- 物事を正しく行うことと、物事を今すぐ行うことには違いがあります。理想的には前者を実行する必要がありますが、現実の世界では後者も必要です。その良い例として、できるだけ早くリリースする必要があるセキュリティ修正があります。緊急の修正であるマージリクエストで、作成者に対して大規模なリファクタリング実行の依頼は避けるべきです。 -- 今日物事をうまく行うことは、大抵、明日何かを完璧に行うことよりも良いものです。一方、間に合わせのものを今日出荷すると、大抵、明日ましなものを出すよりも事態が悪化します。適切なバランスを見つけることができない場合は、他の人に意見を求めてください。 - -### GitLab 固有の考慮事項 - -GitLabは多くの場所で使用されています。多くのユーザーが[Omnibus パッケージ](https://about.gitlab.com/install/)を使用していますが、[Dockerイメージ](../install/docker/_index.md)を使用する人もいれば[ソースからインストール](../install/installation.md)する人もいますし、他のインストール方法もあります。GitLab.com自体は大規模なEnterprise Editionのインスタンスです。これにはいくつかの意味合いがあります。 - -1. **クエリを変更**した場合、GitLab.comの規模でパフォーマンスが悪化しないことを確認するために、次のようなテストする必要があります。 - 1. ローカルで大量のデータを生成してみます。 - 1. GitLab.comからのクエリプランの要求は、その検証に最も信頼性の高い方法です。 -1. **データベースの移行**においては、以下を確認します。 - 1. 可逆的であること。 - 1. GitLab.comの規模でパフォーマンスが高いこと。確信がない場合は、メンテナーにステージング環境で移行をテストするように依頼します。 - 1. 正しく分類されていること。 - - 標準の移行は、新しいコードをインスタンスで実行する前に実施します。 - - [デプロイ後の移行](database/post_deployment_migrations.md)は、インスタンスをそのように構成している場合、新しいコードをデプロイした_後_に実行します。 - - [バッチ化したバックグラウンド移行](database/batched_background_migrations.md)はSidekiqで実行し、[デプロイ後の移行時間制限](migration_style_guide.md#how-long-a-migration-should-take)GitLab.comスケールを超える移行に使用する必要があります。 -1. **Sidekiqワーカー**は、[下位互換性のない方法では変更できません](sidekiq/compatibility_across_updates.md)。 - 1. デプロイを行う前にSidekiqキューをドレインしないため、キューには以前のバージョンのGitLabからのワーカーが残っています。 - 1. メソッドシグネチャを変更する必要がある場合は、2つのリリースで変更し、最初のリリースで新旧両方の引数を受け入れるようにします。 - 1. 同様に、ワーカーを削除する必要がある場合は、1つのリリースでスケジューリングを停止してから、次のリリースで削除します。こうすると既存のジョブを実行できます。 - 1. すべてのインスタンスがすべての中間バージョンにアップグレードされるわけではないことにご注意ください（ユーザーによってはX.1.0からX.10.0に移行したり、より大幅なアップグレードを試す可能性があります）。よって古いフォーマットの受け入れが困難でなければ、そうしてください。 -1. **キャッシュした値**は、リリースをまたいで永続化される場合があります。キャッシュした値が返すタイプを変更する場合（たとえば文字列やnilから配列に）、同時にキャッシュキーを変更します。 -1. **設定**の追加は[最後の手段](https://handbook.gitlab.com/handbook/product/product-principles/#convention-over-configuration)とすべきです。[GitLab Railsへの新しい設定の追加](architecture.md#adding-a-new-setting-in-gitlab-rails)を参照してください。 -1. **ファイルシステムへのアクセス**は、[クラウドネイティブアーキテクチャ](architecture.md#adapting-existing-and-introducing-new-components)ではできません。実行する必要のあるファイルストレージに対して、オブジェクトストレージをサポートしていることを確認します。詳細については、[アップロードのドキュメント](uploads/_index.md)を参照してください。 - -### お客様にとって重要なマージリクエスト - -マージリクエストは、それを行うとビジネスに大きなメリットがあるため、お客様が重要な優先事項と見なすこということから、利点が生まれます。 - -お客様にとって重要なマージリクエストの性質: - -- 開発のシニアディレクター以上が、あるマージリクエストがお客様にとって極めて重要であるとの評価を承認する必要があります。あるいは2人の直属の部下が承認した場合も、承認として機能します。 -- DRIは、`customer-critical-merge-request`ラベルをマージリクエストに付けます。 -- お客様にとって重要なマージリクエストに関与するレビュアーとメンテナーは、この決定が下されたらすぐに関与する必要があります。 -- お客様にとって重要なマージリクエストに関与する人の作業を優先して、彼らがそれに集中するために必要な時間を確保する必要があります。 -- お客様にとって重要なマージリクエストに取り組む際は、GitLabの[価値観](https://handbook.gitlab.com/handbook/values/)とプロセスを遵守し、家族や友人を最優先して仕事を二の次とし、完了の定義、イテレーション、準備ができたらリリースすることに特に注意する必要があります。 -- お客様にとって重要なマージリクエストでは、[技術的な決定を優先する](https://handbook.gitlab.com/handbook/engineering/development/principles/#prioritizing-technical-decisions)プロセスごとに、セキュリティを低下させたり、データ損失のリスクをもたらしたり、可用性を低下させたり、既存の機能を損なったりしないようにする必要があります。 -- お客様にとって重要なリクエストについては、関与する人がたとえ[効率](https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/#evaluating-efficiency)を犠牲にする_場合がある_としても、マージまでの経過時間を短縮できると考えているのであれば、Zoom、Slackには同期して、さらにマージリクエストのコメントには非同期での調整を_検討_することを_推奨_しています。 -- お客様にとって重要なマージリクエストをマージした後、将来のお客様にとって重要となるマージリクエストの頻度の低減を目的として、レトロスペクティブを完了する必要があります。 - -## パイプラインの失敗のトラブルシューティング - -パイプラインが、実施したコード変更とは関係のない理由で失敗する場合があります。そういった事例の一部を、考えられる解決策とともに以下に示します。 - -レビューやヘルプを求めるには、パイプラインを通す必要はないことを常に覚えておいてください。パイプラインが通らず、その理由がわからない場合は、お気軽にチームに連絡するか、テキストとして`@gitlab-bot help`を使用してMRにコメントを残してMRコーチに支援を求めるか、`contribute`チャンネルで[コミュニティディスコード](https://discord.gg/gitlab)に連絡してください。 - -- **変更とは関係がないと思われる理由でテストに失敗した場合**: デフォルトブランチでも発生するかを確認します。その場合、「マスターの破損」が原因であるため、デフォルトブランチでの障害の修正を待つ必要があります。修正後にブランチをリベースするか、[マージした結果のパイプライン](../ci/pipelines/merged_results_pipelines.md)が有効になっていれば、単に別のパイプラインを実行します。 -- **`danger-review` ジョブが失敗した場合**: MRに20を超えるコミットがあるか確認します。その場合は、コミット数が少なくなるようにリベースしてスカッシュするか、`danger-review`ジョブを再度実行します。一時的な障害が発生しただけかもしれません。 - -## 例 - -コードレビューの実施方法は、新しいコントリビューターを驚かせるかもしれません。何が期待されているかの理解に役立つコードレビューの例を次に示します。 - -**[「デザインに再利用するために`DiffNote`を変更」](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/13703): **改行に関する細かい点から、デザインのバージョンとは何か、特定のファイル（親と空白の`sha`と 空のツリー）の以前のバージョンがない場合にどのように比較するかについてまで、それにはすべてが含まれていました。 - -**[「複数行の提案をサポート」](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/25211)**:MR自体はFEとBEの間のコラボレーションで構成されており、レビュアーへの作成者のコメントを文書化しています。いくつかの細かい点、情報に関するいくつかの質問、そして最後にはセキュリティの脆弱性を記述しています。 - -**[「プロジェクトごとに複数のリポジトリを許可する」](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/10251)**: ZJは、これがおそらく影響を与える他のプロジェクト（workhorse）を参照して、一貫性を保つための改善点をいくつか提案しました。そしてJamesのコメントは、全体的なコード品質（委任の使用、`&.`などのタイプ）に役立ち、コードをより堅牢化しました。 - -**[「マージリクエストの複数の担当者をサポートする」](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/10161)**: コードベースの複数の部分に影響するMRでのコラボレーションの優良例。Nickは興味深いエッジケースを指摘し、James Lopezもインポート/エクスポート機能に関する懸念の提起に関与しました。 - -### クレジット - -主に[`thoughtbot`コードレビューガイド](https://github.com/thoughtbot/guides/tree/main/code-review)に基づいています。 diff --git a/doc-locale/ja-jp/development/code_suggestions/_index.md b/doc-locale/ja-jp/development/code_suggestions/_index.md new file mode 100644 index 00000000000..ac635ee8d6e --- /dev/null +++ b/doc-locale/ja-jp/development/code_suggestions/_index.md @@ -0,0 +1,4 @@ +--- +redirect_to: '../ai_features/code_suggestions.md' +remove_date: '2025-06-05' +--- diff --git a/doc-locale/ja-jp/development/contributing/_index.md b/doc-locale/ja-jp/development/contributing/_index.md new file mode 100644 index 00000000000..6f9495cfb27 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Contribute to GitLab development +--- diff --git a/doc-locale/ja-jp/development/contributing/design.md b/doc-locale/ja-jp/development/contributing/design.md new file mode 100644 index 00000000000..6a6aa349608 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/design.md @@ -0,0 +1,6 @@ +--- +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. +title: Design and user interface changes +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/_index.md b/doc-locale/ja-jp/development/contributing/first_contribution/_index.md new file mode 100644 index 00000000000..c935f50db09 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: 'Tutorial: Make a GitLab contribution' +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md new file mode 100644 index 00000000000..cb535e4dc47 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md @@ -0,0 +1,6 @@ +--- +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. +title: Configure GDK-in-a-box +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk.md b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk.md new file mode 100644 index 00000000000..912d6e621ab --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gdk.md @@ -0,0 +1,6 @@ +--- +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. +title: Install the GDK development environment +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gitpod.md b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gitpod.md new file mode 100644 index 00000000000..3639f22b784 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/configure-dev-env-gitpod.md @@ -0,0 +1,6 @@ +--- +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. +title: Configure the Gitpod development environment +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gdk.md b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gdk.md new file mode 100644 index 00000000000..479ba9de9b1 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gdk.md @@ -0,0 +1,6 @@ +--- +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. +title: Contribute code with GDK +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gitpod.md b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gitpod.md new file mode 100644 index 00000000000..0c56982f704 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-gitpod.md @@ -0,0 +1,6 @@ +--- +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. +title: Contribute code with Gitpod +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/contribute-web-ide.md b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-web-ide.md new file mode 100644 index 00000000000..ba8e06aebec --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/contribute-web-ide.md @@ -0,0 +1,6 @@ +--- +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. +title: Contribute code with the Web IDE +--- diff --git a/doc-locale/ja-jp/development/contributing/first_contribution/mr-review.md b/doc-locale/ja-jp/development/contributing/first_contribution/mr-review.md new file mode 100644 index 00000000000..135fc734685 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/first_contribution/mr-review.md @@ -0,0 +1,6 @@ +--- +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. +title: Create a merge request +--- diff --git a/doc-locale/ja-jp/development/contributing/issue_workflow.md b/doc-locale/ja-jp/development/contributing/issue_workflow.md new file mode 100644 index 00000000000..32fd1135a9e --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/issue_workflow.md @@ -0,0 +1,6 @@ +--- +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. +title: Issues workflow +--- diff --git a/doc-locale/ja-jp/development/contributing/merge_request_coaches.md b/doc-locale/ja-jp/development/contributing/merge_request_coaches.md new file mode 100644 index 00000000000..017ce50efa8 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/merge_request_coaches.md @@ -0,0 +1,6 @@ +--- +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. +title: How GitLab Merge Request Coaches can help you +--- diff --git a/doc-locale/ja-jp/development/contributing/merge_request_workflow.md b/doc-locale/ja-jp/development/contributing/merge_request_workflow.md new file mode 100644 index 00000000000..6be16238120 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/merge_request_workflow.md @@ -0,0 +1,6 @@ +--- +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. +title: Merge requests workflow +--- diff --git a/doc-locale/ja-jp/development/contributing/style_guides.md b/doc-locale/ja-jp/development/contributing/style_guides.md new file mode 100644 index 00000000000..3131e80f17a --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/style_guides.md @@ -0,0 +1,6 @@ +--- +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. +title: Development style guides +--- diff --git a/doc-locale/ja-jp/development/contributing/verify/_index.md b/doc-locale/ja-jp/development/contributing/verify/_index.md new file mode 100644 index 00000000000..7bf80b2c412 --- /dev/null +++ b/doc-locale/ja-jp/development/contributing/verify/_index.md @@ -0,0 +1,5 @@ +--- +stage: Verify +group: Pipeline Execution +title: Contribute to Verify stage codebase +--- diff --git a/doc-locale/ja-jp/development/cookies.md b/doc-locale/ja-jp/development/cookies.md new file mode 100644 index 00000000000..95b1bef09b2 --- /dev/null +++ b/doc-locale/ja-jp/development/cookies.md @@ -0,0 +1,6 @@ +--- +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. +title: Cookies +--- diff --git a/doc-locale/ja-jp/development/dangerbot.md b/doc-locale/ja-jp/development/dangerbot.md new file mode 100644 index 00000000000..52f9b1d72a8 --- /dev/null +++ b/doc-locale/ja-jp/development/dangerbot.md @@ -0,0 +1,6 @@ +--- +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. +title: Danger bot +--- diff --git a/doc-locale/ja-jp/development/data_retention_policies.md b/doc-locale/ja-jp/development/data_retention_policies.md new file mode 100644 index 00000000000..15007dc8540 --- /dev/null +++ b/doc-locale/ja-jp/development/data_retention_policies.md @@ -0,0 +1,6 @@ +--- +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. +title: Data Retention Guidelines for Feature Development +--- diff --git a/doc-locale/ja-jp/development/data_science/_index.md b/doc-locale/ja-jp/development/data_science/_index.md new file mode 100644 index 00000000000..5bb8cde9fe4 --- /dev/null +++ b/doc-locale/ja-jp/development/data_science/_index.md @@ -0,0 +1,6 @@ +--- +stage: ModelOps +group: MLOps +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. +title: Data Science +--- diff --git a/doc-locale/ja-jp/development/data_science/model_registry/_index.md b/doc-locale/ja-jp/development/data_science/model_registry/_index.md new file mode 100644 index 00000000000..c52ab14a4eb --- /dev/null +++ b/doc-locale/ja-jp/development/data_science/model_registry/_index.md @@ -0,0 +1,6 @@ +--- +stage: ModelOps +group: MLOps +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. +title: Model Registry +--- diff --git a/doc-locale/ja-jp/development/data_seeder.md b/doc-locale/ja-jp/development/data_seeder.md new file mode 100644 index 00000000000..64e31a1c9dd --- /dev/null +++ b/doc-locale/ja-jp/development/data_seeder.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +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: Data Seeder test data harness created by the Test Data Working Group https://handbook.gitlab.com/handbook/company/working-groups/demo-test-data/ +title: Data Seeder +--- diff --git a/doc-locale/ja-jp/development/database/_index.md b/doc-locale/ja-jp/development/database/_index.md new file mode 100644 index 00000000000..5096d503a59 --- /dev/null +++ b/doc-locale/ja-jp/development/database/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Database development guidelines +--- diff --git a/doc-locale/ja-jp/development/database/add_foreign_key_to_existing_column.md b/doc-locale/ja-jp/development/database/add_foreign_key_to_existing_column.md new file mode 100644 index 00000000000..be1d995490b --- /dev/null +++ b/doc-locale/ja-jp/development/database/add_foreign_key_to_existing_column.md @@ -0,0 +1,4 @@ +--- +redirect_to: 'foreign_keys.md' +remove_date: '2025-03-28' +--- diff --git a/doc-locale/ja-jp/development/database/adding_database_indexes.md b/doc-locale/ja-jp/development/database/adding_database_indexes.md new file mode 100644 index 00000000000..bd13a3f858f --- /dev/null +++ b/doc-locale/ja-jp/development/database/adding_database_indexes.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Adding Database Indexes +--- diff --git a/doc-locale/ja-jp/development/database/avoiding_downtime_in_migrations.md b/doc-locale/ja-jp/development/database/avoiding_downtime_in_migrations.md new file mode 100644 index 00000000000..2247cdfda7b --- /dev/null +++ b/doc-locale/ja-jp/development/database/avoiding_downtime_in_migrations.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Avoiding downtime in migrations +--- diff --git a/doc-locale/ja-jp/development/database/batched_background_migrations.md b/doc-locale/ja-jp/development/database/batched_background_migrations.md new file mode 100644 index 00000000000..d3a5ebe64be --- /dev/null +++ b/doc-locale/ja-jp/development/database/batched_background_migrations.md @@ -0,0 +1,6 @@ +--- +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' +title: Batched background migrations +--- diff --git a/doc-locale/ja-jp/development/database/batching_best_practices.md b/doc-locale/ja-jp/development/database/batching_best_practices.md new file mode 100644 index 00000000000..cec65962a56 --- /dev/null +++ b/doc-locale/ja-jp/development/database/batching_best_practices.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Batching best practices +--- diff --git a/doc-locale/ja-jp/development/database/ci_mirrored_tables.md b/doc-locale/ja-jp/development/database/ci_mirrored_tables.md new file mode 100644 index 00000000000..26a9401eebb --- /dev/null +++ b/doc-locale/ja-jp/development/database/ci_mirrored_tables.md @@ -0,0 +1,6 @@ +--- +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. +title: CI mirrored tables +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/_index.md b/doc-locale/ja-jp/development/database/clickhouse/_index.md new file mode 100644 index 00000000000..9455056b7b1 --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/_index.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Introduction to ClickHouse use and table design +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/clickhouse_within_gitlab.md b/doc-locale/ja-jp/development/database/clickhouse/clickhouse_within_gitlab.md new file mode 100644 index 00000000000..986ef78ce8d --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/clickhouse_within_gitlab.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: ClickHouse within GitLab +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/gitlab_activity_data.md b/doc-locale/ja-jp/development/database/clickhouse/gitlab_activity_data.md new file mode 100644 index 00000000000..4023a6cd5d1 --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/gitlab_activity_data.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Store GitLab activity data in ClickHouse +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/merge_request_analytics.md b/doc-locale/ja-jp/development/database/clickhouse/merge_request_analytics.md new file mode 100644 index 00000000000..a8fe7e674aa --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/merge_request_analytics.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Merge request analytics with ClickHouse +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/optimization.md b/doc-locale/ja-jp/development/database/clickhouse/optimization.md new file mode 100644 index 00000000000..8b21e0291a6 --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/optimization.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Optimizing query execution +--- diff --git a/doc-locale/ja-jp/development/database/clickhouse/tiered_storage.md b/doc-locale/ja-jp/development/database/clickhouse/tiered_storage.md new file mode 100644 index 00000000000..ee39d1ba12f --- /dev/null +++ b/doc-locale/ja-jp/development/database/clickhouse/tiered_storage.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Tiered Storages in ClickHouse +--- diff --git a/doc-locale/ja-jp/development/database/client_side_connection_pool.md b/doc-locale/ja-jp/development/database/client_side_connection_pool.md new file mode 100644 index 00000000000..bfb79ccfda7 --- /dev/null +++ b/doc-locale/ja-jp/development/database/client_side_connection_pool.md @@ -0,0 +1,6 @@ +--- +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. +title: Client-side connection-pool +--- diff --git a/doc-locale/ja-jp/development/database/constraint_naming_convention.md b/doc-locale/ja-jp/development/database/constraint_naming_convention.md new file mode 100644 index 00000000000..fd3c07b30a8 --- /dev/null +++ b/doc-locale/ja-jp/development/database/constraint_naming_convention.md @@ -0,0 +1,6 @@ +--- +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. +title: Constraints naming conventions +--- diff --git a/doc-locale/ja-jp/development/database/creating_enums.md b/doc-locale/ja-jp/development/database/creating_enums.md new file mode 100644 index 00000000000..93d42c850cc --- /dev/null +++ b/doc-locale/ja-jp/development/database/creating_enums.md @@ -0,0 +1,6 @@ +--- +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. +title: Creating enums +--- diff --git a/doc-locale/ja-jp/development/database/database_debugging.md b/doc-locale/ja-jp/development/database/database_debugging.md new file mode 100644 index 00000000000..f4249a01154 --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_debugging.md @@ -0,0 +1,6 @@ +--- +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. +title: Troubleshooting and debugging the database +--- diff --git a/doc-locale/ja-jp/development/database/database_dictionary.md b/doc-locale/ja-jp/development/database/database_dictionary.md new file mode 100644 index 00000000000..7c0dcab609e --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_dictionary.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Database Dictionary +--- diff --git a/doc-locale/ja-jp/development/database/database_lab.md b/doc-locale/ja-jp/development/database/database_lab.md new file mode 100644 index 00000000000..0aecd56dd34 --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_lab.md @@ -0,0 +1,8 @@ +--- +type: reference, howto +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: Database access for engineers and related parties. +title: Database Lab and Postgres.ai +--- diff --git a/doc-locale/ja-jp/development/database/database_lab_pgai.md b/doc-locale/ja-jp/development/database/database_lab_pgai.md new file mode 100644 index 00000000000..520fba3594e --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_lab_pgai.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Database Lab access using the `pgai` Ruby gem +--- diff --git a/doc-locale/ja-jp/development/database/database_migration_pipeline.md b/doc-locale/ja-jp/development/database/database_migration_pipeline.md new file mode 100644 index 00000000000..1f1d1f289ba --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_migration_pipeline.md @@ -0,0 +1,6 @@ +--- +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. +title: Database migration pipeline +--- diff --git a/doc-locale/ja-jp/development/database/database_query_comments.md b/doc-locale/ja-jp/development/database/database_query_comments.md new file mode 100644 index 00000000000..62b11b4852a --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_query_comments.md @@ -0,0 +1,6 @@ +--- +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. +title: Database query comments with Marginalia +--- diff --git a/doc-locale/ja-jp/development/database/database_reviewer_guidelines.md b/doc-locale/ja-jp/development/database/database_reviewer_guidelines.md new file mode 100644 index 00000000000..42c333770dc --- /dev/null +++ b/doc-locale/ja-jp/development/database/database_reviewer_guidelines.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Database Reviewer Guidelines +--- diff --git a/doc-locale/ja-jp/development/database/db_dump.md b/doc-locale/ja-jp/development/database/db_dump.md new file mode 100644 index 00000000000..3e2cbdbadb4 --- /dev/null +++ b/doc-locale/ja-jp/development/database/db_dump.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Importing a database dump into a staging environment +--- diff --git a/doc-locale/ja-jp/development/database/dbcheck-migrations-job.md b/doc-locale/ja-jp/development/database/dbcheck-migrations-job.md new file mode 100644 index 00000000000..eb8d6a04caf --- /dev/null +++ b/doc-locale/ja-jp/development/database/dbcheck-migrations-job.md @@ -0,0 +1,6 @@ +--- +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. +title: db:check-migrations job +--- diff --git a/doc-locale/ja-jp/development/database/dbmigrate_multi_version_upgrade_job.md b/doc-locale/ja-jp/development/database/dbmigrate_multi_version_upgrade_job.md new file mode 100644 index 00000000000..9c18bc77eb8 --- /dev/null +++ b/doc-locale/ja-jp/development/database/dbmigrate_multi_version_upgrade_job.md @@ -0,0 +1,6 @@ +--- +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. +title: db:migrate:multi-version-upgrade job +--- diff --git a/doc-locale/ja-jp/development/database/deduplicate_database_records.md b/doc-locale/ja-jp/development/database/deduplicate_database_records.md new file mode 100644 index 00000000000..fd926841edb --- /dev/null +++ b/doc-locale/ja-jp/development/database/deduplicate_database_records.md @@ -0,0 +1,6 @@ +--- +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. +title: Deduplicate database records in a database table +--- diff --git a/doc-locale/ja-jp/development/database/deleting_migrations.md b/doc-locale/ja-jp/development/database/deleting_migrations.md new file mode 100644 index 00000000000..354111eec9c --- /dev/null +++ b/doc-locale/ja-jp/development/database/deleting_migrations.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Delete existing migrations +--- diff --git a/doc-locale/ja-jp/development/database/efficient_in_operator_queries.md b/doc-locale/ja-jp/development/database/efficient_in_operator_queries.md new file mode 100644 index 00000000000..886c60afb42 --- /dev/null +++ b/doc-locale/ja-jp/development/database/efficient_in_operator_queries.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Efficient `IN` operator queries +--- diff --git a/doc-locale/ja-jp/development/database/filtering_by_label.md b/doc-locale/ja-jp/development/database/filtering_by_label.md new file mode 100644 index 00000000000..bdc3924d898 --- /dev/null +++ b/doc-locale/ja-jp/development/database/filtering_by_label.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Project Management +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +title: Filtering by label +--- diff --git a/doc-locale/ja-jp/development/database/foreign_keys.md b/doc-locale/ja-jp/development/database/foreign_keys.md new file mode 100644 index 00000000000..fa6fda83de5 --- /dev/null +++ b/doc-locale/ja-jp/development/database/foreign_keys.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Foreign keys and associations +--- diff --git a/doc-locale/ja-jp/development/database/hash_indexes.md b/doc-locale/ja-jp/development/database/hash_indexes.md new file mode 100644 index 00000000000..c907f460743 --- /dev/null +++ b/doc-locale/ja-jp/development/database/hash_indexes.md @@ -0,0 +1,6 @@ +--- +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. +title: Hash Indexes +--- diff --git a/doc-locale/ja-jp/development/database/insert_into_tables_in_batches.md b/doc-locale/ja-jp/development/database/insert_into_tables_in_batches.md new file mode 100644 index 00000000000..3de3eaf388c --- /dev/null +++ b/doc-locale/ja-jp/development/database/insert_into_tables_in_batches.md @@ -0,0 +1,7 @@ +--- +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` in Rails 6, which operates at the row level (that is, using `Hash`es), GitLab has added a set of APIs that make it safe and simple to insert ActiveRecord objects in bulk. +title: Insert into tables in batches +--- diff --git a/doc-locale/ja-jp/development/database/iterating_tables_in_batches.md b/doc-locale/ja-jp/development/database/iterating_tables_in_batches.md new file mode 100644 index 00000000000..4ecf6c8b6d9 --- /dev/null +++ b/doc-locale/ja-jp/development/database/iterating_tables_in_batches.md @@ -0,0 +1,6 @@ +--- +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. +title: Iterating tables in batches +--- diff --git a/doc-locale/ja-jp/development/database/keyset_pagination.md b/doc-locale/ja-jp/development/database/keyset_pagination.md new file mode 100644 index 00000000000..ace3232d9ce --- /dev/null +++ b/doc-locale/ja-jp/development/database/keyset_pagination.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Keyset pagination +--- diff --git a/doc-locale/ja-jp/development/database/large_tables_limitations.md b/doc-locale/ja-jp/development/database/large_tables_limitations.md new file mode 100644 index 00000000000..687707dd659 --- /dev/null +++ b/doc-locale/ja-jp/development/database/large_tables_limitations.md @@ -0,0 +1,6 @@ +--- +stage: Data Access +group: Database Frameworks +info: Any user with at least the Maintainer role can merge updates to this content. +title: Large tables limitations +--- diff --git a/doc-locale/ja-jp/development/database/layout_and_access_patterns.md b/doc-locale/ja-jp/development/database/layout_and_access_patterns.md new file mode 100644 index 00000000000..790d91f2ddf --- /dev/null +++ b/doc-locale/ja-jp/development/database/layout_and_access_patterns.md @@ -0,0 +1,6 @@ +--- +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. +title: Best practices for data layout and access patterns +--- diff --git a/doc-locale/ja-jp/development/database/load_balancing.md b/doc-locale/ja-jp/development/database/load_balancing.md new file mode 100644 index 00000000000..a66213d8344 --- /dev/null +++ b/doc-locale/ja-jp/development/database/load_balancing.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Database load balancing +--- diff --git a/doc-locale/ja-jp/development/database/loose_foreign_keys.md b/doc-locale/ja-jp/development/database/loose_foreign_keys.md new file mode 100644 index 00000000000..d9e6eaac7d4 --- /dev/null +++ b/doc-locale/ja-jp/development/database/loose_foreign_keys.md @@ -0,0 +1,6 @@ +--- +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. +title: Loose foreign keys +--- diff --git a/doc-locale/ja-jp/development/database/maintenance_operations.md b/doc-locale/ja-jp/development/database/maintenance_operations.md new file mode 100644 index 00000000000..bc061465355 --- /dev/null +++ b/doc-locale/ja-jp/development/database/maintenance_operations.md @@ -0,0 +1,6 @@ +--- +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. +title: Maintenance operations +--- diff --git a/doc-locale/ja-jp/development/database/migration_ordering.md b/doc-locale/ja-jp/development/database/migration_ordering.md new file mode 100644 index 00000000000..c122980f8f3 --- /dev/null +++ b/doc-locale/ja-jp/development/database/migration_ordering.md @@ -0,0 +1,6 @@ +--- +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. +title: Migration ordering +--- diff --git a/doc-locale/ja-jp/development/database/migration_squashing.md b/doc-locale/ja-jp/development/database/migration_squashing.md new file mode 100644 index 00000000000..8a23a13062a --- /dev/null +++ b/doc-locale/ja-jp/development/database/migration_squashing.md @@ -0,0 +1,6 @@ +--- +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. +title: Migration Squashing +--- diff --git a/doc-locale/ja-jp/development/database/migrations_for_multiple_databases.md b/doc-locale/ja-jp/development/database/migrations_for_multiple_databases.md new file mode 100644 index 00000000000..c83e4aef9ed --- /dev/null +++ b/doc-locale/ja-jp/development/database/migrations_for_multiple_databases.md @@ -0,0 +1,6 @@ +--- +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. +title: Migrations for Multiple databases +--- diff --git a/doc-locale/ja-jp/development/database/multiple_databases.md b/doc-locale/ja-jp/development/database/multiple_databases.md new file mode 100644 index 00000000000..f5e04c1e674 --- /dev/null +++ b/doc-locale/ja-jp/development/database/multiple_databases.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Cells Infrastructure +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. +title: Multiple Databases +--- diff --git a/doc-locale/ja-jp/development/database/namespaces_storage_statistics.md b/doc-locale/ja-jp/development/database/namespaces_storage_statistics.md new file mode 100644 index 00000000000..0eab4b6ff86 --- /dev/null +++ b/doc-locale/ja-jp/development/database/namespaces_storage_statistics.md @@ -0,0 +1,6 @@ +--- +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. +title: 'Database case study: Namespaces storage statistics' +--- diff --git a/doc-locale/ja-jp/development/database/new_database_migration_version.md b/doc-locale/ja-jp/development/database/new_database_migration_version.md new file mode 100644 index 00000000000..0b71fd5bc13 --- /dev/null +++ b/doc-locale/ja-jp/development/database/new_database_migration_version.md @@ -0,0 +1,6 @@ +--- +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. +title: Introducing a new database migration version +--- diff --git a/doc-locale/ja-jp/development/database/not_null_constraints.md b/doc-locale/ja-jp/development/database/not_null_constraints.md new file mode 100644 index 00000000000..b90584a4999 --- /dev/null +++ b/doc-locale/ja-jp/development/database/not_null_constraints.md @@ -0,0 +1,6 @@ +--- +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. +title: '`NOT NULL` constraints' +--- diff --git a/doc-locale/ja-jp/development/database/offset_pagination_optimization.md b/doc-locale/ja-jp/development/database/offset_pagination_optimization.md new file mode 100644 index 00000000000..976ed18e0e3 --- /dev/null +++ b/doc-locale/ja-jp/development/database/offset_pagination_optimization.md @@ -0,0 +1,6 @@ +--- +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. +title: Offset pagination optimization +--- diff --git a/doc-locale/ja-jp/development/database/ordering_table_columns.md b/doc-locale/ja-jp/development/database/ordering_table_columns.md new file mode 100644 index 00000000000..f3e13518190 --- /dev/null +++ b/doc-locale/ja-jp/development/database/ordering_table_columns.md @@ -0,0 +1,6 @@ +--- +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. +title: Ordering Table Columns in PostgreSQL +--- diff --git a/doc-locale/ja-jp/development/database/pagination_guidelines.md b/doc-locale/ja-jp/development/database/pagination_guidelines.md new file mode 100644 index 00000000000..a9cbac2b0fe --- /dev/null +++ b/doc-locale/ja-jp/development/database/pagination_guidelines.md @@ -0,0 +1,6 @@ +--- +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. +title: Pagination guidelines +--- diff --git a/doc-locale/ja-jp/development/database/pagination_performance_guidelines.md b/doc-locale/ja-jp/development/database/pagination_performance_guidelines.md new file mode 100644 index 00000000000..ba8e9f153a9 --- /dev/null +++ b/doc-locale/ja-jp/development/database/pagination_performance_guidelines.md @@ -0,0 +1,6 @@ +--- +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. +title: Pagination performance guidelines +--- diff --git a/doc-locale/ja-jp/development/database/partitioning/_index.md b/doc-locale/ja-jp/development/database/partitioning/_index.md new file mode 100644 index 00000000000..72942d53b33 --- /dev/null +++ b/doc-locale/ja-jp/development/database/partitioning/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Database table partitioning +--- diff --git a/doc-locale/ja-jp/development/database/partitioning/date_range.md b/doc-locale/ja-jp/development/database/partitioning/date_range.md new file mode 100644 index 00000000000..23a9d712960 --- /dev/null +++ b/doc-locale/ja-jp/development/database/partitioning/date_range.md @@ -0,0 +1,6 @@ +--- +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. +title: Date range partitioning +--- diff --git a/doc-locale/ja-jp/development/database/partitioning/hash.md b/doc-locale/ja-jp/development/database/partitioning/hash.md new file mode 100644 index 00000000000..59c77531175 --- /dev/null +++ b/doc-locale/ja-jp/development/database/partitioning/hash.md @@ -0,0 +1,6 @@ +--- +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. +title: Hash Partitioning +--- diff --git a/doc-locale/ja-jp/development/database/partitioning/int_range.md b/doc-locale/ja-jp/development/database/partitioning/int_range.md new file mode 100644 index 00000000000..7c6bd3e4d3d --- /dev/null +++ b/doc-locale/ja-jp/development/database/partitioning/int_range.md @@ -0,0 +1,6 @@ +--- +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. +title: Int range partitioning +--- diff --git a/doc-locale/ja-jp/development/database/partitioning/list.md b/doc-locale/ja-jp/development/database/partitioning/list.md new file mode 100644 index 00000000000..969bfe9e6c0 --- /dev/null +++ b/doc-locale/ja-jp/development/database/partitioning/list.md @@ -0,0 +1,6 @@ +--- +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. +title: List partition +--- diff --git a/doc-locale/ja-jp/development/database/poc_tree_iterator.md b/doc-locale/ja-jp/development/database/poc_tree_iterator.md new file mode 100644 index 00000000000..172764c01a1 --- /dev/null +++ b/doc-locale/ja-jp/development/database/poc_tree_iterator.md @@ -0,0 +1,6 @@ +--- +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. +title: Batch iteration in a tree hierarchy (proof of concept) +--- diff --git a/doc-locale/ja-jp/development/database/polymorphic_associations.md b/doc-locale/ja-jp/development/database/polymorphic_associations.md new file mode 100644 index 00000000000..ff2c7979d16 --- /dev/null +++ b/doc-locale/ja-jp/development/database/polymorphic_associations.md @@ -0,0 +1,6 @@ +--- +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. +title: Polymorphic Associations +--- diff --git a/doc-locale/ja-jp/development/database/post_deployment_migrations.md b/doc-locale/ja-jp/development/database/post_deployment_migrations.md new file mode 100644 index 00000000000..1ba3a5a762a --- /dev/null +++ b/doc-locale/ja-jp/development/database/post_deployment_migrations.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Post Deployment Migrations +--- diff --git a/doc-locale/ja-jp/development/database/query_count_limits.md b/doc-locale/ja-jp/development/database/query_count_limits.md new file mode 100644 index 00000000000..81e88b2e92e --- /dev/null +++ b/doc-locale/ja-jp/development/database/query_count_limits.md @@ -0,0 +1,6 @@ +--- +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. +title: Query Count Limits +--- diff --git a/doc-locale/ja-jp/development/database/query_performance.md b/doc-locale/ja-jp/development/database/query_performance.md new file mode 100644 index 00000000000..655659eeed7 --- /dev/null +++ b/doc-locale/ja-jp/development/database/query_performance.md @@ -0,0 +1,6 @@ +--- +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. +title: Query performance guidelines +--- diff --git a/doc-locale/ja-jp/development/database/query_recorder.md b/doc-locale/ja-jp/development/database/query_recorder.md new file mode 100644 index 00000000000..eabd14703b3 --- /dev/null +++ b/doc-locale/ja-jp/development/database/query_recorder.md @@ -0,0 +1,6 @@ +--- +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. +title: QueryRecorder +--- diff --git a/doc-locale/ja-jp/development/database/rename_database_tables.md b/doc-locale/ja-jp/development/database/rename_database_tables.md new file mode 100644 index 00000000000..8641c2c06c5 --- /dev/null +++ b/doc-locale/ja-jp/development/database/rename_database_tables.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Rename table without downtime +--- diff --git a/doc-locale/ja-jp/development/database/required_stops.md b/doc-locale/ja-jp/development/database/required_stops.md new file mode 100644 index 00000000000..e752b21df71 --- /dev/null +++ b/doc-locale/ja-jp/development/database/required_stops.md @@ -0,0 +1,6 @@ +--- +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. +title: Database required stops +--- diff --git a/doc-locale/ja-jp/development/database/scalability/patterns/_index.md b/doc-locale/ja-jp/development/database/scalability/patterns/_index.md new file mode 100644 index 00000000000..28a5ea26e01 --- /dev/null +++ b/doc-locale/ja-jp/development/database/scalability/patterns/_index.md @@ -0,0 +1,7 @@ +--- +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 +description: Learn how to scale the database through the use of best-of-class database scalability patterns +title: Database Scalability Patterns +--- diff --git a/doc-locale/ja-jp/development/database/scalability/patterns/read_mostly.md b/doc-locale/ja-jp/development/database/scalability/patterns/read_mostly.md new file mode 100644 index 00000000000..9e9c4154345 --- /dev/null +++ b/doc-locale/ja-jp/development/database/scalability/patterns/read_mostly.md @@ -0,0 +1,7 @@ +--- +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 +description: Learn how to scale operating on read-mostly data at scale +title: Read-mostly data +--- diff --git a/doc-locale/ja-jp/development/database/scalability/patterns/time_decay.md b/doc-locale/ja-jp/development/database/scalability/patterns/time_decay.md new file mode 100644 index 00000000000..ef2cd0b5903 --- /dev/null +++ b/doc-locale/ja-jp/development/database/scalability/patterns/time_decay.md @@ -0,0 +1,7 @@ +--- +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 +description: Learn how to operate on large time-decay data +title: Time-decay data +--- diff --git a/doc-locale/ja-jp/development/database/serializing_data.md b/doc-locale/ja-jp/development/database/serializing_data.md new file mode 100644 index 00000000000..4b40a8975bc --- /dev/null +++ b/doc-locale/ja-jp/development/database/serializing_data.md @@ -0,0 +1,6 @@ +--- +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. +title: Serializing Data +--- diff --git a/doc-locale/ja-jp/development/database/setting_multiple_values.md b/doc-locale/ja-jp/development/database/setting_multiple_values.md new file mode 100644 index 00000000000..74ba665f543 --- /dev/null +++ b/doc-locale/ja-jp/development/database/setting_multiple_values.md @@ -0,0 +1,6 @@ +--- +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. +title: Update multiple database objects +--- diff --git a/doc-locale/ja-jp/development/database/sha1_as_binary.md b/doc-locale/ja-jp/development/database/sha1_as_binary.md new file mode 100644 index 00000000000..da2fea7a81d --- /dev/null +++ b/doc-locale/ja-jp/development/database/sha1_as_binary.md @@ -0,0 +1,6 @@ +--- +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. +title: Storing SHA1 Hashes As Binary +--- diff --git a/doc-locale/ja-jp/development/database/single_table_inheritance.md b/doc-locale/ja-jp/development/database/single_table_inheritance.md new file mode 100644 index 00000000000..6370d5b97d0 --- /dev/null +++ b/doc-locale/ja-jp/development/database/single_table_inheritance.md @@ -0,0 +1,6 @@ +--- +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. +title: Single Table Inheritance +--- diff --git a/doc-locale/ja-jp/development/database/strings_and_the_text_data_type.md b/doc-locale/ja-jp/development/database/strings_and_the_text_data_type.md new file mode 100644 index 00000000000..17e6976941f --- /dev/null +++ b/doc-locale/ja-jp/development/database/strings_and_the_text_data_type.md @@ -0,0 +1,6 @@ +--- +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. +title: Strings and the Text data type +--- diff --git a/doc-locale/ja-jp/development/database/swapping_tables.md b/doc-locale/ja-jp/development/database/swapping_tables.md new file mode 100644 index 00000000000..b430783db42 --- /dev/null +++ b/doc-locale/ja-jp/development/database/swapping_tables.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Swapping Tables +--- diff --git a/doc-locale/ja-jp/development/database/transaction_guidelines.md b/doc-locale/ja-jp/development/database/transaction_guidelines.md new file mode 100644 index 00000000000..d4d9874f2dd --- /dev/null +++ b/doc-locale/ja-jp/development/database/transaction_guidelines.md @@ -0,0 +1,6 @@ +--- +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. +title: Transaction guidelines +--- diff --git a/doc-locale/ja-jp/development/database/understanding_explain_plans.md b/doc-locale/ja-jp/development/database/understanding_explain_plans.md new file mode 100644 index 00000000000..c27d7729832 --- /dev/null +++ b/doc-locale/ja-jp/development/database/understanding_explain_plans.md @@ -0,0 +1,6 @@ +--- +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. +title: Understanding EXPLAIN plans +--- diff --git a/doc-locale/ja-jp/development/database/verifying_database_capabilities.md b/doc-locale/ja-jp/development/database/verifying_database_capabilities.md new file mode 100644 index 00000000000..6f5fc731256 --- /dev/null +++ b/doc-locale/ja-jp/development/database/verifying_database_capabilities.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Verifying Database Capabilities +--- diff --git a/doc-locale/ja-jp/development/database/virtual_tables.md b/doc-locale/ja-jp/development/database/virtual_tables.md new file mode 100644 index 00000000000..00ed829a013 --- /dev/null +++ b/doc-locale/ja-jp/development/database/virtual_tables.md @@ -0,0 +1,6 @@ +--- +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. +title: SQL views +--- diff --git a/doc-locale/ja-jp/development/database_review.md b/doc-locale/ja-jp/development/database_review.md new file mode 100644 index 00000000000..c4696f96b5c --- /dev/null +++ b/doc-locale/ja-jp/development/database_review.md @@ -0,0 +1,6 @@ +--- +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. +title: Database Review Guidelines +--- diff --git a/doc-locale/ja-jp/development/deleting_data.md b/doc-locale/ja-jp/development/deleting_data.md new file mode 100644 index 00000000000..c867ba2e63d --- /dev/null +++ b/doc-locale/ja-jp/development/deleting_data.md @@ -0,0 +1,6 @@ +--- +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. +title: Data deletion guidelines +--- diff --git a/doc-locale/ja-jp/development/dependencies.md b/doc-locale/ja-jp/development/dependencies.md new file mode 100644 index 00000000000..2f6b62d89a6 --- /dev/null +++ b/doc-locale/ja-jp/development/dependencies.md @@ -0,0 +1,6 @@ +--- +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. +title: Dependencies +--- diff --git a/doc-locale/ja-jp/development/deprecation_guidelines/_index.md b/doc-locale/ja-jp/development/deprecation_guidelines/_index.md new file mode 100644 index 00000000000..09d645dac65 --- /dev/null +++ b/doc-locale/ja-jp/development/deprecation_guidelines/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Deprecating GitLab features +--- diff --git a/doc-locale/ja-jp/development/developing_with_solargraph.md b/doc-locale/ja-jp/development/developing_with_solargraph.md new file mode 100644 index 00000000000..fed63e8aef4 --- /dev/null +++ b/doc-locale/ja-jp/development/developing_with_solargraph.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Using Solargraph +--- diff --git a/doc-locale/ja-jp/development/development_processes.md b/doc-locale/ja-jp/development/development_processes.md new file mode 100644 index 00000000000..88ed1936e45 --- /dev/null +++ b/doc-locale/ja-jp/development/development_processes.md @@ -0,0 +1,6 @@ +--- +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. +title: Development processes +--- diff --git a/doc-locale/ja-jp/development/development_seed_files.md b/doc-locale/ja-jp/development/development_seed_files.md new file mode 100644 index 00000000000..1c6bd633129 --- /dev/null +++ b/doc-locale/ja-jp/development/development_seed_files.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Development seed files +--- diff --git a/doc-locale/ja-jp/development/distributed_tracing.md b/doc-locale/ja-jp/development/distributed_tracing.md new file mode 100644 index 00000000000..90640fef03a --- /dev/null +++ b/doc-locale/ja-jp/development/distributed_tracing.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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. +title: Distributed tracing development guidelines +--- diff --git a/doc-locale/ja-jp/development/distribution/_index.md b/doc-locale/ja-jp/development/distribution/_index.md new file mode 100644 index 00000000000..c117bbdccfe --- /dev/null +++ b/doc-locale/ja-jp/development/distribution/_index.md @@ -0,0 +1,7 @@ +--- +stage: Systems +group: Distribution +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: Development guidelines for Distribution +title: Contribute to GitLab Distribution +--- diff --git a/doc-locale/ja-jp/development/documentation/_index.md b/doc-locale/ja-jp/development/documentation/_index.md new file mode 100644 index 00000000000..4e19cbcd69f --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/_index.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Contribute to the GitLab documentation +--- diff --git a/doc-locale/ja-jp/development/documentation/authoring_environment.md b/doc-locale/ja-jp/development/documentation/authoring_environment.md new file mode 100644 index 00000000000..d47a39319b2 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/authoring_environment.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Set up your authoring environment +--- diff --git a/doc-locale/ja-jp/development/documentation/backporting.md b/doc-locale/ja-jp/development/documentation/backporting.md new file mode 100644 index 00000000000..319f68997cb --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/backporting.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Backport documentation changes +--- diff --git a/doc-locale/ja-jp/development/documentation/drawers.md b/doc-locale/ja-jp/development/documentation/drawers.md new file mode 100644 index 00000000000..647e2779e02 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/drawers.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Create content for drawers +--- diff --git a/doc-locale/ja-jp/development/documentation/experiment_beta.md b/doc-locale/ja-jp/development/documentation/experiment_beta.md new file mode 100644 index 00000000000..1975bcc18b0 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/experiment_beta.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects +title: Documenting experimental and beta features +--- diff --git a/doc-locale/ja-jp/development/documentation/feature_flags.md b/doc-locale/ja-jp/development/documentation/feature_flags.md new file mode 100644 index 00000000000..2892abd4f78 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/feature_flags.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: GitLab development - how to document features deployed behind feature flags +title: Document features deployed behind feature flags +--- diff --git a/doc-locale/ja-jp/development/documentation/graphql_styleguide.md b/doc-locale/ja-jp/development/documentation/graphql_styleguide.md new file mode 100644 index 00000000000..9ae5dd17d6c --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/graphql_styleguide.md @@ -0,0 +1,7 @@ +--- +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. +description: Writing styles, markup, formatting, and other standards for GraphQL API's GitLab Documentation. +title: Creating a GraphQL example page +--- diff --git a/doc-locale/ja-jp/development/documentation/help.md b/doc-locale/ja-jp/development/documentation/help.md new file mode 100644 index 00000000000..c0fca17fe94 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/help.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: GitLab /help +--- diff --git a/doc-locale/ja-jp/development/documentation/hugo_migration.md b/doc-locale/ja-jp/development/documentation/hugo_migration.md new file mode 100644 index 00000000000..e894fd51d65 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/hugo_migration.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Hugo migration reference for writers +--- diff --git a/doc-locale/ja-jp/development/documentation/metadata.md b/doc-locale/ja-jp/development/documentation/metadata.md new file mode 100644 index 00000000000..02069df2df1 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/metadata.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Metadata +--- diff --git a/doc-locale/ja-jp/development/documentation/redirects.md b/doc-locale/ja-jp/development/documentation/redirects.md new file mode 100644 index 00000000000..f1363aa007f --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/redirects.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to contribute to GitLab Documentation. +title: Redirects in GitLab documentation +--- diff --git a/doc-locale/ja-jp/development/documentation/restful_api_styleguide.md b/doc-locale/ja-jp/development/documentation/restful_api_styleguide.md new file mode 100644 index 00000000000..828089e5f52 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/restful_api_styleguide.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Writing styles, markup, formatting, and other standards for the GitLab RESTful APIs. +title: Documenting REST API resources +--- diff --git a/doc-locale/ja-jp/development/documentation/review_apps.md b/doc-locale/ja-jp/development/documentation/review_apps.md new file mode 100644 index 00000000000..a8d283acfe4 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/review_apps.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how documentation review apps work. +title: Documentation review apps +--- diff --git a/doc-locale/ja-jp/development/documentation/site_architecture/_index.md b/doc-locale/ja-jp/development/documentation/site_architecture/_index.md new file mode 100644 index 00000000000..9d02c7bc2c4 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/site_architecture/_index.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Documentation site architecture +--- diff --git a/doc-locale/ja-jp/development/documentation/site_architecture/automation.md b/doc-locale/ja-jp/development/documentation/site_architecture/automation.md new file mode 100644 index 00000000000..8fa2724cc33 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/site_architecture/automation.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Automated pages +--- diff --git a/doc-locale/ja-jp/development/documentation/site_architecture/deployment_process.md b/doc-locale/ja-jp/development/documentation/site_architecture/deployment_process.md new file mode 100644 index 00000000000..67a91e3da9d --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/site_architecture/deployment_process.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Documentation deployments +--- diff --git a/doc-locale/ja-jp/development/documentation/site_architecture/folder_structure.md b/doc-locale/ja-jp/development/documentation/site_architecture/folder_structure.md new file mode 100644 index 00000000000..22fe1e850f9 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/site_architecture/folder_structure.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Folder structure for documentation +--- diff --git a/doc-locale/ja-jp/development/documentation/site_architecture/global_nav.md b/doc-locale/ja-jp/development/documentation/site_architecture/global_nav.md new file mode 100644 index 00000000000..e709dab08de --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/site_architecture/global_nav.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how GitLab docs' global navigation works and how to add new items. +title: Global navigation +--- diff --git a/doc-locale/ja-jp/development/documentation/styleguide/_index.md b/doc-locale/ja-jp/development/documentation/styleguide/_index.md new file mode 100644 index 00000000000..51e78e1f72b --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/styleguide/_index.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Writing styles, markup, formatting, and other standards for GitLab Documentation. +title: Documentation Style Guide +--- diff --git a/doc-locale/ja-jp/development/documentation/styleguide/availability_details.md b/doc-locale/ja-jp/development/documentation/styleguide/availability_details.md new file mode 100644 index 00000000000..cf0c645a752 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/styleguide/availability_details.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Writing styles, markup, formatting, and other standards for GitLab Documentation. +title: Product availability details +--- diff --git a/doc-locale/ja-jp/development/documentation/styleguide/deprecations_and_removals.md b/doc-locale/ja-jp/development/documentation/styleguide/deprecations_and_removals.md new file mode 100644 index 00000000000..0828b63f2b7 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/styleguide/deprecations_and_removals.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Guidelines for deprecations and page removals +title: Deprecations and removals +--- diff --git a/doc-locale/ja-jp/development/documentation/styleguide/word_list.md b/doc-locale/ja-jp/development/documentation/styleguide/word_list.md new file mode 100644 index 00000000000..171b47554c5 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/styleguide/word_list.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Writing styles, markup, formatting, and other standards for GitLab Documentation. +title: Recommended word list +--- diff --git a/doc-locale/ja-jp/development/documentation/testing/_index.md b/doc-locale/ja-jp/development/documentation/testing/_index.md new file mode 100644 index 00000000000..270d3e05802 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/testing/_index.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to contribute to GitLab Documentation. +title: Documentation testing +--- diff --git a/doc-locale/ja-jp/development/documentation/testing/links.md b/doc-locale/ja-jp/development/documentation/testing/links.md new file mode 100644 index 00000000000..a74844a65a4 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/testing/links.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to contribute to GitLab Documentation. +title: Documentation and UI link tests +--- diff --git a/doc-locale/ja-jp/development/documentation/testing/markdownlint.md b/doc-locale/ja-jp/development/documentation/testing/markdownlint.md new file mode 100644 index 00000000000..cf881ccb84b --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/testing/markdownlint.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to contribute to GitLab Documentation. +title: markdownlint documentation tests +--- diff --git a/doc-locale/ja-jp/development/documentation/testing/vale.md b/doc-locale/ja-jp/development/documentation/testing/vale.md new file mode 100644 index 00000000000..deb186581fd --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/testing/vale.md @@ -0,0 +1,7 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to contribute to GitLab Documentation. +title: Vale documentation tests +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/_index.md b/doc-locale/ja-jp/development/documentation/topic_types/_index.md new file mode 100644 index 00000000000..fd65e601861 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/_index.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Documentation topic types (CTRT) +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/concept.md b/doc-locale/ja-jp/development/documentation/topic_types/concept.md new file mode 100644 index 00000000000..176eb798c25 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/concept.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Concept topic type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/get_started.md b/doc-locale/ja-jp/development/documentation/topic_types/get_started.md new file mode 100644 index 00000000000..2818332fd3e --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/get_started.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Style Guide +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Get started page type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/glossary.md b/doc-locale/ja-jp/development/documentation/topic_types/glossary.md new file mode 100644 index 00000000000..7856464bca2 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/glossary.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Glossary topic type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/reference.md b/doc-locale/ja-jp/development/documentation/topic_types/reference.md new file mode 100644 index 00000000000..c82f6ce692c --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/reference.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Reference topic type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/task.md b/doc-locale/ja-jp/development/documentation/topic_types/task.md new file mode 100644 index 00000000000..d8a46e2338b --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/task.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Task topic type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/top_level_page.md b/doc-locale/ja-jp/development/documentation/topic_types/top_level_page.md new file mode 100644 index 00000000000..3847b793761 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/top_level_page.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Top-level page type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/troubleshooting.md b/doc-locale/ja-jp/development/documentation/topic_types/troubleshooting.md new file mode 100644 index 00000000000..22fb15207d3 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/troubleshooting.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Troubleshooting topic type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/tutorial.md b/doc-locale/ja-jp/development/documentation/topic_types/tutorial.md new file mode 100644 index 00000000000..71dadfb776c --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/tutorial.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Documentation Guidelines +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Tutorial page type +--- diff --git a/doc-locale/ja-jp/development/documentation/topic_types/version_specific_changes.md b/doc-locale/ja-jp/development/documentation/topic_types/version_specific_changes.md new file mode 100644 index 00000000000..a87be649ef3 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/topic_types/version_specific_changes.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +description: Learn how to document version-specific changes +title: Version-specific changes +--- diff --git a/doc-locale/ja-jp/development/documentation/workflow.md b/doc-locale/ja-jp/development/documentation/workflow.md new file mode 100644 index 00000000000..60e26b23e85 --- /dev/null +++ b/doc-locale/ja-jp/development/documentation/workflow.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: For assistance with this Style Guide page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-other-projects-and-subjects. +title: Documentation workflow +--- diff --git a/doc-locale/ja-jp/development/duo_workflow/_index.md b/doc-locale/ja-jp/development/duo_workflow/_index.md new file mode 100644 index 00000000000..92b079ae976 --- /dev/null +++ b/doc-locale/ja-jp/development/duo_workflow/_index.md @@ -0,0 +1,6 @@ +--- +stage: AI-powered +group: Duo Workflow +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. +title: Development of GitLab Duo Workflow +--- diff --git a/doc-locale/ja-jp/development/duo_workflow/create_triage_policy_with_gitlab_duo_workflow_guide.md b/doc-locale/ja-jp/development/duo_workflow/create_triage_policy_with_gitlab_duo_workflow_guide.md new file mode 100644 index 00000000000..0fdb90f8e77 --- /dev/null +++ b/doc-locale/ja-jp/development/duo_workflow/create_triage_policy_with_gitlab_duo_workflow_guide.md @@ -0,0 +1,3 @@ +--- +title: Create triage policies with the assistance of GitLab Duo Workflow +--- diff --git a/doc-locale/ja-jp/development/ee_features.md b/doc-locale/ja-jp/development/ee_features.md new file mode 100644 index 00000000000..00c2443d7a5 --- /dev/null +++ b/doc-locale/ja-jp/development/ee_features.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Guidelines for implementing Enterprise Edition features +--- diff --git a/doc-locale/ja-jp/development/emails.md b/doc-locale/ja-jp/development/emails.md new file mode 100644 index 00000000000..3a7cf1be377 --- /dev/null +++ b/doc-locale/ja-jp/development/emails.md @@ -0,0 +1,6 @@ +--- +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. +title: Working with email in development +--- diff --git a/doc-locale/ja-jp/development/enabling_features_on_dedicated.md b/doc-locale/ja-jp/development/enabling_features_on_dedicated.md new file mode 100644 index 00000000000..c82ba7263a1 --- /dev/null +++ b/doc-locale/ja-jp/development/enabling_features_on_dedicated.md @@ -0,0 +1,6 @@ +--- +stage: GitLab Dedicated +group: Environment Automation +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. +title: Enabling features for GitLab Dedicated +--- diff --git a/doc-locale/ja-jp/development/event_store.md b/doc-locale/ja-jp/development/event_store.md new file mode 100644 index 00000000000..6f4ee12f3f5 --- /dev/null +++ b/doc-locale/ja-jp/development/event_store.md @@ -0,0 +1,6 @@ +--- +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. +title: GitLab EventStore +--- diff --git a/doc-locale/ja-jp/development/experiment_guide/_index.md b/doc-locale/ja-jp/development/experiment_guide/_index.md new file mode 100644 index 00000000000..500296b171f --- /dev/null +++ b/doc-locale/ja-jp/development/experiment_guide/_index.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +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. +title: Experiment Guide +--- diff --git a/doc-locale/ja-jp/development/experiment_guide/experiment_code_reviews.md b/doc-locale/ja-jp/development/experiment_guide/experiment_code_reviews.md new file mode 100644 index 00000000000..d4e4a62b73f --- /dev/null +++ b/doc-locale/ja-jp/development/experiment_guide/experiment_code_reviews.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +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. +title: Experiment code reviews +--- diff --git a/doc-locale/ja-jp/development/experiment_guide/experiment_rollout.md b/doc-locale/ja-jp/development/experiment_guide/experiment_rollout.md new file mode 100644 index 00000000000..9a77f83f4a9 --- /dev/null +++ b/doc-locale/ja-jp/development/experiment_guide/experiment_rollout.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +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. +title: Experiment rollouts and feature flags +--- diff --git a/doc-locale/ja-jp/development/experiment_guide/implementing_experiments.md b/doc-locale/ja-jp/development/experiment_guide/implementing_experiments.md new file mode 100644 index 00000000000..22f838931d1 --- /dev/null +++ b/doc-locale/ja-jp/development/experiment_guide/implementing_experiments.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +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. +title: Implementing an A/B/n experiment +--- diff --git a/doc-locale/ja-jp/development/experiment_guide/testing_experiments.md b/doc-locale/ja-jp/development/experiment_guide/testing_experiments.md new file mode 100644 index 00000000000..846cc5a8a75 --- /dev/null +++ b/doc-locale/ja-jp/development/experiment_guide/testing_experiments.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +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. +title: Testing experiments +--- diff --git a/doc-locale/ja-jp/development/export_csv.md b/doc-locale/ja-jp/development/export_csv.md new file mode 100644 index 00000000000..acdae827115 --- /dev/null +++ b/doc-locale/ja-jp/development/export_csv.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Export to CSV +--- diff --git a/doc-locale/ja-jp/development/fe_guide/_index.md b/doc-locale/ja-jp/development/fe_guide/_index.md new file mode 100644 index 00000000000..a167602983a --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend Development Guidelines +--- diff --git a/doc-locale/ja-jp/development/fe_guide/accessibility/_index.md b/doc-locale/ja-jp/development/fe_guide/accessibility/_index.md new file mode 100644 index 00000000000..6a386f4b40a --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/accessibility/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Accessibility +--- diff --git a/doc-locale/ja-jp/development/fe_guide/accessibility/automated_testing.md b/doc-locale/ja-jp/development/fe_guide/accessibility/automated_testing.md new file mode 100644 index 00000000000..caadfcf8daf --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/accessibility/automated_testing.md @@ -0,0 +1,6 @@ +--- +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. +title: Automated accessibility testing +--- diff --git a/doc-locale/ja-jp/development/fe_guide/accessibility/best_practices.md b/doc-locale/ja-jp/development/fe_guide/accessibility/best_practices.md new file mode 100644 index 00000000000..51ef60067ea --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/accessibility/best_practices.md @@ -0,0 +1,6 @@ +--- +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. +title: Accessibility best practices +--- diff --git a/doc-locale/ja-jp/development/fe_guide/analytics_dashboards.md b/doc-locale/ja-jp/development/fe_guide/analytics_dashboards.md new file mode 100644 index 00000000000..0e642794033 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/analytics_dashboards.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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. +title: Analytics dashboards +--- diff --git a/doc-locale/ja-jp/development/fe_guide/architecture.md b/doc-locale/ja-jp/development/fe_guide/architecture.md new file mode 100644 index 00000000000..640adcc6166 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/architecture.md @@ -0,0 +1,6 @@ +--- +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. +title: Architecture +--- diff --git a/doc-locale/ja-jp/development/fe_guide/axios.md b/doc-locale/ja-jp/development/fe_guide/axios.md new file mode 100644 index 00000000000..0376651d047 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/axios.md @@ -0,0 +1,6 @@ +--- +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. +title: Axios +--- diff --git a/doc-locale/ja-jp/development/fe_guide/blob_syntax_highlighting.md b/doc-locale/ja-jp/development/fe_guide/blob_syntax_highlighting.md new file mode 100644 index 00000000000..c6b4a5f2360 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/blob_syntax_highlighting.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Syntax highlighting development guidelines (repository blob viewer) +--- diff --git a/doc-locale/ja-jp/development/fe_guide/content_editor.md b/doc-locale/ja-jp/development/fe_guide/content_editor.md new file mode 100644 index 00000000000..b16aaec1a3d --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/content_editor.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Knowledge +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. +title: Rich text editor development guidelines +--- diff --git a/doc-locale/ja-jp/development/fe_guide/dark_mode.md b/doc-locale/ja-jp/development/fe_guide/dark_mode.md new file mode 100644 index 00000000000..bf6385f79d7 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/dark_mode.md @@ -0,0 +1,6 @@ +--- +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. +title: Dark mode +--- diff --git a/doc-locale/ja-jp/development/fe_guide/date_and_time.md b/doc-locale/ja-jp/development/fe_guide/date_and_time.md new file mode 100644 index 00000000000..db09b29b695 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/date_and_time.md @@ -0,0 +1,6 @@ +--- +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. +title: Date and time +--- diff --git a/doc-locale/ja-jp/development/fe_guide/dependencies.md b/doc-locale/ja-jp/development/fe_guide/dependencies.md new file mode 100644 index 00000000000..bf60e680adc --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/dependencies.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend dependencies +--- diff --git a/doc-locale/ja-jp/development/fe_guide/design_patterns.md b/doc-locale/ja-jp/development/fe_guide/design_patterns.md new file mode 100644 index 00000000000..50141b3b049 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/design_patterns.md @@ -0,0 +1,6 @@ +--- +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. +title: Design Patterns +--- diff --git a/doc-locale/ja-jp/development/fe_guide/design_tokens.md b/doc-locale/ja-jp/development/fe_guide/design_tokens.md new file mode 100644 index 00000000000..cb1b8f76b22 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/design_tokens.md @@ -0,0 +1,6 @@ +--- +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. +title: Design tokens +--- diff --git a/doc-locale/ja-jp/development/fe_guide/diagrams_net_integration.md b/doc-locale/ja-jp/development/fe_guide/diagrams_net_integration.md new file mode 100644 index 00000000000..1bf06b07648 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/diagrams_net_integration.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Knowledge +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. +title: Diagrams.net integration +--- diff --git a/doc-locale/ja-jp/development/fe_guide/emojis.md b/doc-locale/ja-jp/development/fe_guide/emojis.md new file mode 100644 index 00000000000..03f48d1ca13 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/emojis.md @@ -0,0 +1,6 @@ +--- +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. +title: Emojis +--- diff --git a/doc-locale/ja-jp/development/fe_guide/frontend_faq.md b/doc-locale/ja-jp/development/fe_guide/frontend_faq.md new file mode 100644 index 00000000000..62a379d025c --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/frontend_faq.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend FAQ +--- diff --git a/doc-locale/ja-jp/development/fe_guide/frontend_goals.md b/doc-locale/ja-jp/development/fe_guide/frontend_goals.md new file mode 100644 index 00000000000..b2046db94c8 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/frontend_goals.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend Goals +--- diff --git a/doc-locale/ja-jp/development/fe_guide/getting_started.md b/doc-locale/ja-jp/development/fe_guide/getting_started.md new file mode 100644 index 00000000000..e7eddfff6c6 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/getting_started.md @@ -0,0 +1,6 @@ +--- +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. +title: Getting started +--- diff --git a/doc-locale/ja-jp/development/fe_guide/graphql.md b/doc-locale/ja-jp/development/fe_guide/graphql.md new file mode 100644 index 00000000000..1049833d944 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/graphql.md @@ -0,0 +1,6 @@ +--- +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. +title: GraphQL +--- diff --git a/doc-locale/ja-jp/development/fe_guide/guides.md b/doc-locale/ja-jp/development/fe_guide/guides.md new file mode 100644 index 00000000000..dbc07378c46 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/guides.md @@ -0,0 +1,6 @@ +--- +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. +title: Guides +--- diff --git a/doc-locale/ja-jp/development/fe_guide/haml.md b/doc-locale/ja-jp/development/fe_guide/haml.md new file mode 100644 index 00000000000..aae64c5a369 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/haml.md @@ -0,0 +1,6 @@ +--- +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. +title: HAML +--- diff --git a/doc-locale/ja-jp/development/fe_guide/icons.md b/doc-locale/ja-jp/development/fe_guide/icons.md new file mode 100644 index 00000000000..dcc392295a7 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/icons.md @@ -0,0 +1,6 @@ +--- +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. +title: Icons and SVG Illustrations +--- diff --git a/doc-locale/ja-jp/development/fe_guide/keyboard_shortcuts.md b/doc-locale/ja-jp/development/fe_guide/keyboard_shortcuts.md new file mode 100644 index 00000000000..6ca9a9193c2 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/keyboard_shortcuts.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Personal Productivity +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. +title: Implementing keyboard shortcuts +--- diff --git a/doc-locale/ja-jp/development/fe_guide/logging.md b/doc-locale/ja-jp/development/fe_guide/logging.md new file mode 100644 index 00000000000..102e6a96515 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/logging.md @@ -0,0 +1,6 @@ +--- +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. +title: Client-side logging for frontend development +--- diff --git a/doc-locale/ja-jp/development/fe_guide/merge_request_widgets.md b/doc-locale/ja-jp/development/fe_guide/merge_request_widgets.md new file mode 100644 index 00000000000..4da6f2fbc17 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/merge_request_widgets.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +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: Developer documentation for extending the merge request report widget with additional features. +title: Merge request widgets +--- diff --git a/doc-locale/ja-jp/development/fe_guide/migrating_from_vuex.md b/doc-locale/ja-jp/development/fe_guide/migrating_from_vuex.md new file mode 100644 index 00000000000..8586cb996a3 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/migrating_from_vuex.md @@ -0,0 +1,6 @@ +--- +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. +title: Migrating from Vuex +--- diff --git a/doc-locale/ja-jp/development/fe_guide/onboarding_course/_index.md b/doc-locale/ja-jp/development/fe_guide/onboarding_course/_index.md new file mode 100644 index 00000000000..798001cf6ba --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/onboarding_course/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend onboarding course +--- diff --git a/doc-locale/ja-jp/development/fe_guide/onboarding_course/lesson_1.md b/doc-locale/ja-jp/development/fe_guide/onboarding_course/lesson_1.md new file mode 100644 index 00000000000..9205e8ebebf --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/onboarding_course/lesson_1.md @@ -0,0 +1,6 @@ +--- +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. +title: Lesson 1 +--- diff --git a/doc-locale/ja-jp/development/fe_guide/performance.md b/doc-locale/ja-jp/development/fe_guide/performance.md new file mode 100644 index 00000000000..284640d5937 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/performance.md @@ -0,0 +1,6 @@ +--- +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. +title: Performance +--- diff --git a/doc-locale/ja-jp/development/fe_guide/pinia.md b/doc-locale/ja-jp/development/fe_guide/pinia.md new file mode 100644 index 00000000000..e56cd4c6388 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/pinia.md @@ -0,0 +1,6 @@ +--- +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. +title: Pinia +--- diff --git a/doc-locale/ja-jp/development/fe_guide/registry_architecture.md b/doc-locale/ja-jp/development/fe_guide/registry_architecture.md new file mode 100644 index 00000000000..5241bd988b0 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/registry_architecture.md @@ -0,0 +1,6 @@ +--- +stage: Package +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. +title: Registry architecture +--- diff --git a/doc-locale/ja-jp/development/fe_guide/security.md b/doc-locale/ja-jp/development/fe_guide/security.md new file mode 100644 index 00000000000..3f7a453b569 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/security.md @@ -0,0 +1,6 @@ +--- +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. +title: Security +--- diff --git a/doc-locale/ja-jp/development/fe_guide/sentry.md b/doc-locale/ja-jp/development/fe_guide/sentry.md new file mode 100644 index 00000000000..f3c1414e71b --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/sentry.md @@ -0,0 +1,6 @@ +--- +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. +title: Sentry monitoring in the frontend development of GitLab +--- diff --git a/doc-locale/ja-jp/development/fe_guide/source_editor.md b/doc-locale/ja-jp/development/fe_guide/source_editor.md new file mode 100644 index 00000000000..d34bd7541d4 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/source_editor.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Source Editor +--- diff --git a/doc-locale/ja-jp/development/fe_guide/state_management.md b/doc-locale/ja-jp/development/fe_guide/state_management.md new file mode 100644 index 00000000000..bcecb1be614 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/state_management.md @@ -0,0 +1,6 @@ +--- +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. +title: State management guidance +--- diff --git a/doc-locale/ja-jp/development/fe_guide/storybook.md b/doc-locale/ja-jp/development/fe_guide/storybook.md new file mode 100644 index 00000000000..91d6f736875 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/storybook.md @@ -0,0 +1,6 @@ +--- +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. +title: Storybook +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/_index.md b/doc-locale/ja-jp/development/fe_guide/style/_index.md new file mode 100644 index 00000000000..1ea41cb4b79 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend style guides +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/html.md b/doc-locale/ja-jp/development/fe_guide/style/html.md new file mode 100644 index 00000000000..4dd55a1fad7 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/html.md @@ -0,0 +1,6 @@ +--- +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. +title: HTML style guide +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/javascript.md b/doc-locale/ja-jp/development/fe_guide/style/javascript.md new file mode 100644 index 00000000000..9e07d427b84 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/javascript.md @@ -0,0 +1,6 @@ +--- +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. +title: JavaScript style guide +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/scss.md b/doc-locale/ja-jp/development/fe_guide/style/scss.md new file mode 100644 index 00000000000..49f321030b1 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/scss.md @@ -0,0 +1,6 @@ +--- +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. +title: SCSS style guide +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/typescript.md b/doc-locale/ja-jp/development/fe_guide/style/typescript.md new file mode 100644 index 00000000000..abddae83730 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/typescript.md @@ -0,0 +1,6 @@ +--- +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. +title: TypeScript +--- diff --git a/doc-locale/ja-jp/development/fe_guide/style/vue.md b/doc-locale/ja-jp/development/fe_guide/style/vue.md new file mode 100644 index 00000000000..73da87b71ff --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/style/vue.md @@ -0,0 +1,6 @@ +--- +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. +title: Vue.js style guide +--- diff --git a/doc-locale/ja-jp/development/fe_guide/tech_stack.md b/doc-locale/ja-jp/development/fe_guide/tech_stack.md new file mode 100644 index 00000000000..6fdd4c94173 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/tech_stack.md @@ -0,0 +1,6 @@ +--- +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. +title: Tech Stack +--- diff --git a/doc-locale/ja-jp/development/fe_guide/tips_and_tricks.md b/doc-locale/ja-jp/development/fe_guide/tips_and_tricks.md new file mode 100644 index 00000000000..6023ea09204 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/tips_and_tricks.md @@ -0,0 +1,6 @@ +--- +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. +title: Tips and tricks +--- diff --git a/doc-locale/ja-jp/development/fe_guide/tooling.md b/doc-locale/ja-jp/development/fe_guide/tooling.md new file mode 100644 index 00000000000..fc7413f855a --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/tooling.md @@ -0,0 +1,6 @@ +--- +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. +title: Tooling +--- diff --git a/doc-locale/ja-jp/development/fe_guide/troubleshooting.md b/doc-locale/ja-jp/development/fe_guide/troubleshooting.md new file mode 100644 index 00000000000..9515489b3ea --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/troubleshooting.md @@ -0,0 +1,6 @@ +--- +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. +title: Troubleshooting frontend development issues +--- diff --git a/doc-locale/ja-jp/development/fe_guide/type_hinting.md b/doc-locale/ja-jp/development/fe_guide/type_hinting.md new file mode 100644 index 00000000000..9480507741f --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/type_hinting.md @@ -0,0 +1,6 @@ +--- +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. +title: Type hinting overview +--- diff --git a/doc-locale/ja-jp/development/fe_guide/view_component.md b/doc-locale/ja-jp/development/fe_guide/view_component.md new file mode 100644 index 00000000000..1a6f19fb6c4 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/view_component.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Design System +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. +title: ViewComponent +--- diff --git a/doc-locale/ja-jp/development/fe_guide/vue.md b/doc-locale/ja-jp/development/fe_guide/vue.md new file mode 100644 index 00000000000..81523137981 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/vue.md @@ -0,0 +1,6 @@ +--- +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. +title: Vue +--- diff --git a/doc-locale/ja-jp/development/fe_guide/vue3_migration.md b/doc-locale/ja-jp/development/fe_guide/vue3_migration.md new file mode 100644 index 00000000000..af9fd503b2e --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/vue3_migration.md @@ -0,0 +1,6 @@ +--- +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. +title: Migration to Vue 3 +--- diff --git a/doc-locale/ja-jp/development/fe_guide/vuex.md b/doc-locale/ja-jp/development/fe_guide/vuex.md new file mode 100644 index 00000000000..bbc1af40ffd --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/vuex.md @@ -0,0 +1,6 @@ +--- +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. +title: Vuex +--- diff --git a/doc-locale/ja-jp/development/fe_guide/widgets.md b/doc-locale/ja-jp/development/fe_guide/widgets.md new file mode 100644 index 00000000000..077ca932e24 --- /dev/null +++ b/doc-locale/ja-jp/development/fe_guide/widgets.md @@ -0,0 +1,6 @@ +--- +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. +title: Widgets +--- diff --git a/doc-locale/ja-jp/development/feature_categorization/_index.md b/doc-locale/ja-jp/development/feature_categorization/_index.md new file mode 100644 index 00000000000..943e33e5ca2 --- /dev/null +++ b/doc-locale/ja-jp/development/feature_categorization/_index.md @@ -0,0 +1,6 @@ +--- +stage: Enablement +group: Infrastructure +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. +title: Feature Categorization +--- diff --git a/doc-locale/ja-jp/development/feature_development.md b/doc-locale/ja-jp/development/feature_development.md new file mode 100644 index 00000000000..cd2cc63da6f --- /dev/null +++ b/doc-locale/ja-jp/development/feature_development.md @@ -0,0 +1,6 @@ +--- +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. +title: Feature development +--- diff --git a/doc-locale/ja-jp/development/feature_flags/_index.md b/doc-locale/ja-jp/development/feature_flags/_index.md new file mode 100644 index 00000000000..902ed905826 --- /dev/null +++ b/doc-locale/ja-jp/development/feature_flags/_index.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: 'See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines' +description: Developer documentation about GitLab feature flags. +title: Feature flags in the development of GitLab +--- diff --git a/doc-locale/ja-jp/development/feature_flags/controls.md b/doc-locale/ja-jp/development/feature_flags/controls.md new file mode 100644 index 00000000000..43a34a8765b --- /dev/null +++ b/doc-locale/ja-jp/development/feature_flags/controls.md @@ -0,0 +1,6 @@ +--- +stage: none +group: unassigned +info: 'See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines' +title: Use ChatOps to enable and disable feature flags +--- diff --git a/doc-locale/ja-jp/development/features_inside_dot_gitlab.md b/doc-locale/ja-jp/development/features_inside_dot_gitlab.md new file mode 100644 index 00000000000..f65d8dc0f24 --- /dev/null +++ b/doc-locale/ja-jp/development/features_inside_dot_gitlab.md @@ -0,0 +1,6 @@ +--- +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. +title: Features inside the `.gitlab/` directory +--- diff --git a/doc-locale/ja-jp/development/file_storage.md b/doc-locale/ja-jp/development/file_storage.md new file mode 100644 index 00000000000..d455078434b --- /dev/null +++ b/doc-locale/ja-jp/development/file_storage.md @@ -0,0 +1,6 @@ +--- +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. +title: File Storage in GitLab +--- diff --git a/doc-locale/ja-jp/development/fips_gitlab.md b/doc-locale/ja-jp/development/fips_gitlab.md new file mode 100644 index 00000000000..ac291852dda --- /dev/null +++ b/doc-locale/ja-jp/development/fips_gitlab.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: FIPS 140-2 and 140-3 +--- diff --git a/doc-locale/ja-jp/development/gemfile.md b/doc-locale/ja-jp/development/gemfile.md new file mode 100644 index 00000000000..8ca59fa02c7 --- /dev/null +++ b/doc-locale/ja-jp/development/gemfile.md @@ -0,0 +1,6 @@ +--- +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. +title: Gemfile development guidelines +--- diff --git a/doc-locale/ja-jp/development/gems.md b/doc-locale/ja-jp/development/gems.md new file mode 100644 index 00000000000..f40c21f8da1 --- /dev/null +++ b/doc-locale/ja-jp/development/gems.md @@ -0,0 +1,6 @@ +--- +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. +title: Gems development guidelines +--- diff --git a/doc-locale/ja-jp/development/geo.md b/doc-locale/ja-jp/development/geo.md new file mode 100644 index 00000000000..f0cf7b5dd0e --- /dev/null +++ b/doc-locale/ja-jp/development/geo.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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. +title: Geo (development) +--- diff --git a/doc-locale/ja-jp/development/geo/api.md b/doc-locale/ja-jp/development/geo/api.md new file mode 100644 index 00000000000..22dbf2d3acb --- /dev/null +++ b/doc-locale/ja-jp/development/geo/api.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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 +title: Geo API +--- diff --git a/doc-locale/ja-jp/development/geo/framework.md b/doc-locale/ja-jp/development/geo/framework.md new file mode 100644 index 00000000000..13267d112e7 --- /dev/null +++ b/doc-locale/ja-jp/development/geo/framework.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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. +title: Geo self-service framework +--- diff --git a/doc-locale/ja-jp/development/geo/proxying.md b/doc-locale/ja-jp/development/geo/proxying.md new file mode 100644 index 00000000000..89a986ae366 --- /dev/null +++ b/doc-locale/ja-jp/development/geo/proxying.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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. +title: Geo proxying +--- diff --git a/doc-locale/ja-jp/development/git_object_deduplication.md b/doc-locale/ja-jp/development/git_object_deduplication.md new file mode 100644 index 00000000000..5b9172b6830 --- /dev/null +++ b/doc-locale/ja-jp/development/git_object_deduplication.md @@ -0,0 +1,6 @@ +--- +stage: Data Access +group: Gitaly +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. +title: How Git object deduplication works in GitLab +--- diff --git a/doc-locale/ja-jp/development/gitaly.md b/doc-locale/ja-jp/development/gitaly.md new file mode 100644 index 00000000000..11813f7f0ae --- /dev/null +++ b/doc-locale/ja-jp/development/gitaly.md @@ -0,0 +1,6 @@ +--- +stage: Data Access +group: Gitaly +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. +title: Gitaly development guidelines +--- diff --git a/doc-locale/ja-jp/development/github_importer.md b/doc-locale/ja-jp/development/github_importer.md new file mode 100644 index 00000000000..67d346023d1 --- /dev/null +++ b/doc-locale/ja-jp/development/github_importer.md @@ -0,0 +1,6 @@ +--- +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. +title: GitHub importer developer documentation +--- diff --git a/doc-locale/ja-jp/development/gitlab_flavored_markdown/_index.md b/doc-locale/ja-jp/development/gitlab_flavored_markdown/_index.md new file mode 100644 index 00000000000..da132a4a887 --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_flavored_markdown/_index.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: Development guidelines for GitLab Flavored Markdown (GLFM). +title: GitLab Flavored Markdown (GLFM) development guidelines +--- diff --git a/doc-locale/ja-jp/development/gitlab_flavored_markdown/banzai_pipeline_and_parsing.md b/doc-locale/ja-jp/development/gitlab_flavored_markdown/banzai_pipeline_and_parsing.md new file mode 100644 index 00000000000..43c43adad43 --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_flavored_markdown/banzai_pipeline_and_parsing.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: The Banzai pipeline and parsing. +title: The Banzai pipeline and parsing +--- diff --git a/doc-locale/ja-jp/development/gitlab_flavored_markdown/reference_processing.md b/doc-locale/ja-jp/development/gitlab_flavored_markdown/reference_processing.md new file mode 100644 index 00000000000..562d45f1947 --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_flavored_markdown/reference_processing.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: An introduction to reference parsers and reference filters, and a guide to their implementation. +title: Reference processing +--- diff --git a/doc-locale/ja-jp/development/gitlab_shell/_index.md b/doc-locale/ja-jp/development/gitlab_shell/_index.md new file mode 100644 index 00000000000..e0819956c1b --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_shell/_index.md @@ -0,0 +1,6 @@ +--- +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 +title: GitLab Shell development guidelines +--- diff --git a/doc-locale/ja-jp/development/gitlab_shell/features.md b/doc-locale/ja-jp/development/gitlab_shell/features.md new file mode 100644 index 00000000000..83939436821 --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_shell/features.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: GitLab Shell feature list +--- diff --git a/doc-locale/ja-jp/development/gitlab_shell/gitlab_sshd.md b/doc-locale/ja-jp/development/gitlab_shell/gitlab_sshd.md new file mode 100644 index 00000000000..f082bb4ecfb --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_shell/gitlab_sshd.md @@ -0,0 +1,6 @@ +--- +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 +title: '`gitlab-sshd` in GitLab Shell' +--- diff --git a/doc-locale/ja-jp/development/gitlab_shell/process.md b/doc-locale/ja-jp/development/gitlab_shell/process.md new file mode 100644 index 00000000000..ec2903189a4 --- /dev/null +++ b/doc-locale/ja-jp/development/gitlab_shell/process.md @@ -0,0 +1,6 @@ +--- +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 +title: Processes for GitLab Shell +--- diff --git a/doc-locale/ja-jp/development/gitpod_internals.md b/doc-locale/ja-jp/development/gitpod_internals.md new file mode 100644 index 00000000000..bbcdf102c87 --- /dev/null +++ b/doc-locale/ja-jp/development/gitpod_internals.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Engineering Productivity +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. +title: Gitpod internal configuration +--- diff --git a/doc-locale/ja-jp/development/go_guide/_index.md b/doc-locale/ja-jp/development/go_guide/_index.md new file mode 100644 index 00000000000..4c2a6194d93 --- /dev/null +++ b/doc-locale/ja-jp/development/go_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Go standards and style guidelines +--- diff --git a/doc-locale/ja-jp/development/go_guide/dependencies.md b/doc-locale/ja-jp/development/go_guide/dependencies.md new file mode 100644 index 00000000000..3a53b29fb9a --- /dev/null +++ b/doc-locale/ja-jp/development/go_guide/dependencies.md @@ -0,0 +1,6 @@ +--- +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. +title: Dependency Management in Go +--- diff --git a/doc-locale/ja-jp/development/go_guide/go_upgrade.md b/doc-locale/ja-jp/development/go_guide/go_upgrade.md new file mode 100644 index 00000000000..22897efc37d --- /dev/null +++ b/doc-locale/ja-jp/development/go_guide/go_upgrade.md @@ -0,0 +1,6 @@ +--- +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. +title: Managing Go versions +--- diff --git a/doc-locale/ja-jp/development/gotchas.md b/doc-locale/ja-jp/development/gotchas.md new file mode 100644 index 00000000000..389a6ba3211 --- /dev/null +++ b/doc-locale/ja-jp/development/gotchas.md @@ -0,0 +1,6 @@ +--- +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. +title: Gotchas +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/_index.md b/doc-locale/ja-jp/development/graphql_guide/_index.md new file mode 100644 index 00000000000..f689ca0184f --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/_index.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: GraphQL development guidelines +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/authorization.md b/doc-locale/ja-jp/development/graphql_guide/authorization.md new file mode 100644 index 00000000000..bd5e34eafd6 --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/authorization.md @@ -0,0 +1,6 @@ +--- +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. +title: GraphQL Authorization +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/batchloader.md b/doc-locale/ja-jp/development/graphql_guide/batchloader.md new file mode 100644 index 00000000000..f25566251f1 --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/batchloader.md @@ -0,0 +1,6 @@ +--- +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. +title: GraphQL BatchLoader +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/graphql_pro.md b/doc-locale/ja-jp/development/graphql_guide/graphql_pro.md new file mode 100644 index 00000000000..6d111be3a36 --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/graphql_pro.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: GraphQL Pro +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/monitoring.md b/doc-locale/ja-jp/development/graphql_guide/monitoring.md new file mode 100644 index 00000000000..4b50a19c799 --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/monitoring.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Reading GraphQL logs +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/pagination.md b/doc-locale/ja-jp/development/graphql_guide/pagination.md new file mode 100644 index 00000000000..b4ba4f2faf8 --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/pagination.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: GraphQL pagination +--- diff --git a/doc-locale/ja-jp/development/graphql_guide/reviewing.md b/doc-locale/ja-jp/development/graphql_guide/reviewing.md new file mode 100644 index 00000000000..33b4bee421a --- /dev/null +++ b/doc-locale/ja-jp/development/graphql_guide/reviewing.md @@ -0,0 +1,6 @@ +--- +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. +title: GraphQL API merge request checklist +--- diff --git a/doc-locale/ja-jp/development/i18n/_index.md b/doc-locale/ja-jp/development/i18n/_index.md new file mode 100644 index 00000000000..c51d4063755 --- /dev/null +++ b/doc-locale/ja-jp/development/i18n/_index.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Translate GitLab to your language +--- diff --git a/doc-locale/ja-jp/development/i18n/externalization.md b/doc-locale/ja-jp/development/i18n/externalization.md new file mode 100644 index 00000000000..89bea4faf1c --- /dev/null +++ b/doc-locale/ja-jp/development/i18n/externalization.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Internationalization for GitLab +--- diff --git a/doc-locale/ja-jp/development/i18n/merging_translations.md b/doc-locale/ja-jp/development/i18n/merging_translations.md new file mode 100644 index 00000000000..d15cdfaf0e9 --- /dev/null +++ b/doc-locale/ja-jp/development/i18n/merging_translations.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Merging translations from Crowdin +--- diff --git a/doc-locale/ja-jp/development/i18n/proofreader.md b/doc-locale/ja-jp/development/i18n/proofreader.md new file mode 100644 index 00000000000..1eca4ef1414 --- /dev/null +++ b/doc-locale/ja-jp/development/i18n/proofreader.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Proofread Translations +--- diff --git a/doc-locale/ja-jp/development/i18n/translation.md b/doc-locale/ja-jp/development/i18n/translation.md new file mode 100644 index 00000000000..97627ccf0e3 --- /dev/null +++ b/doc-locale/ja-jp/development/i18n/translation.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Translating GitLab +--- diff --git a/doc-locale/ja-jp/development/identity_verification.md b/doc-locale/ja-jp/development/identity_verification.md new file mode 100644 index 00000000000..1148018a612 --- /dev/null +++ b/doc-locale/ja-jp/development/identity_verification.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Identity verification development +--- diff --git a/doc-locale/ja-jp/development/image_scaling.md b/doc-locale/ja-jp/development/image_scaling.md new file mode 100644 index 00000000000..650c3015f15 --- /dev/null +++ b/doc-locale/ja-jp/development/image_scaling.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Organizations +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. +title: Image scaling guide +--- diff --git a/doc-locale/ja-jp/development/import/principles_of_importer_design.md b/doc-locale/ja-jp/development/import/principles_of_importer_design.md new file mode 100644 index 00000000000..6f788073608 --- /dev/null +++ b/doc-locale/ja-jp/development/import/principles_of_importer_design.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Principles of Importer Design +--- diff --git a/doc-locale/ja-jp/development/import_export.md b/doc-locale/ja-jp/development/import_export.md new file mode 100644 index 00000000000..eff0ae0b932 --- /dev/null +++ b/doc-locale/ja-jp/development/import_export.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: Import/Export development documentation +--- diff --git a/doc-locale/ja-jp/development/import_project.md b/doc-locale/ja-jp/development/import_project.md new file mode 100644 index 00000000000..0dc3bdd2338 --- /dev/null +++ b/doc-locale/ja-jp/development/import_project.md @@ -0,0 +1,6 @@ +--- +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. +title: Test import project +--- diff --git a/doc-locale/ja-jp/development/integrations/_index.md b/doc-locale/ja-jp/development/integrations/_index.md new file mode 100644 index 00000000000..a055d374122 --- /dev/null +++ b/doc-locale/ja-jp/development/integrations/_index.md @@ -0,0 +1,7 @@ +--- +stage: Foundations +group: Import and Integrate +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: Development guidelines for Integrations +title: Integration development guidelines +--- diff --git a/doc-locale/ja-jp/development/integrations/jenkins.md b/doc-locale/ja-jp/development/integrations/jenkins.md new file mode 100644 index 00000000000..972ff6d630a --- /dev/null +++ b/doc-locale/ja-jp/development/integrations/jenkins.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: How to run Jenkins in development environment (on macOS) +--- diff --git a/doc-locale/ja-jp/development/integrations/jira_connect.md b/doc-locale/ja-jp/development/integrations/jira_connect.md new file mode 100644 index 00000000000..3cc73cb1445 --- /dev/null +++ b/doc-locale/ja-jp/development/integrations/jira_connect.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Import and Integrate +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. +title: GitLab for Jira Cloud app development +--- diff --git a/doc-locale/ja-jp/development/integrations/secure.md b/doc-locale/ja-jp/development/integrations/secure.md new file mode 100644 index 00000000000..86dcb6b8eb1 --- /dev/null +++ b/doc-locale/ja-jp/development/integrations/secure.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Static Analysis +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. +title: Security scanner integration +--- diff --git a/doc-locale/ja-jp/development/integrations/secure_partner_integration.md b/doc-locale/ja-jp/development/integrations/secure_partner_integration.md new file mode 100644 index 00000000000..f80e96421f2 --- /dev/null +++ b/doc-locale/ja-jp/development/integrations/secure_partner_integration.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Static Analysis +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. +title: Secure Partner Integration - Onboarding Process +--- diff --git a/doc-locale/ja-jp/development/interacting_components.md b/doc-locale/ja-jp/development/interacting_components.md new file mode 100644 index 00000000000..285bf217a49 --- /dev/null +++ b/doc-locale/ja-jp/development/interacting_components.md @@ -0,0 +1,6 @@ +--- +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. +title: Developing against interacting components or features +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/_index.md b/doc-locale/ja-jp/development/internal_analytics/_index.md new file mode 100644 index 00000000000..99e7d530789 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/_index.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Internal analytics +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/browser_sdk.md b/doc-locale/ja-jp/development/internal_analytics/browser_sdk.md new file mode 100644 index 00000000000..a1e2132bb0a --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/browser_sdk.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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 +title: Browser SDK +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/cli_contribution_guidelines.md b/doc-locale/ja-jp/development/internal_analytics/cli_contribution_guidelines.md new file mode 100644 index 00000000000..a472e9974e5 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/cli_contribution_guidelines.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Contributing to the Internal Events CLI +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/instrumentation_layer.md b/doc-locale/ja-jp/development/internal_analytics/instrumentation_layer.md new file mode 100644 index 00000000000..02c7387a266 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/instrumentation_layer.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Single Instrumentation Layer +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/_index.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/_index.md new file mode 100644 index 00000000000..bbe8e3684eb --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/_index.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Internal Event Tracking +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/event_definition_guide.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/event_definition_guide.md new file mode 100644 index 00000000000..b4c1f67d7ad --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/event_definition_guide.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Event definition guide +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/internal_events_payload.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/internal_events_payload.md new file mode 100644 index 00000000000..a705b2198b8 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/internal_events_payload.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Internal Events Payload Samples +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md new file mode 100644 index 00000000000..91d4bc18c12 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Local setup and debugging +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/metric_definition_guide.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/metric_definition_guide.md new file mode 100644 index 00000000000..8d1e9829be7 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/metric_definition_guide.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Metrics definitions +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/migration.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/migration.md new file mode 100644 index 00000000000..9477c69a447 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/migration.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Migrating existing tracking to internal event tracking +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/quick_start.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/quick_start.md new file mode 100644 index 00000000000..8aa3d849a30 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/quick_start.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Quick start for Internal Event Tracking +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/standard_context_fields.md b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/standard_context_fields.md new file mode 100644 index 00000000000..deefa9e06ec --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/internal_event_instrumentation/standard_context_fields.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: GitLab Standard Context Fields +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/metrics/_index.md b/doc-locale/ja-jp/development/internal_analytics/metrics/_index.md new file mode 100644 index 00000000000..d7a5411cafb --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/metrics/_index.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Metrics +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_dictionary.md b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_dictionary.md new file mode 100644 index 00000000000..88d4228b00a --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_dictionary.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Metrics Dictionary Guide +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_instrumentation.md b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_instrumentation.md new file mode 100644 index 00000000000..9f972f002bb --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_instrumentation.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Metrics instrumentation guide +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_lifecycle.md b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_lifecycle.md new file mode 100644 index 00000000000..3207e68d1d7 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/metrics/metrics_lifecycle.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Metric lifecycle +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/product_analytics.md b/doc-locale/ja-jp/development/internal_analytics/product_analytics.md new file mode 100644 index 00000000000..8898d8a1b37 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/product_analytics.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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 +title: Product analytics +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/review_guidelines.md b/doc-locale/ja-jp/development/internal_analytics/review_guidelines.md new file mode 100644 index 00000000000..21f78a4752d --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/review_guidelines.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Internal Analytics review guidelines +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/service_ping/_index.md b/doc-locale/ja-jp/development/internal_analytics/service_ping/_index.md new file mode 100644 index 00000000000..0b6cdef6ce8 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/service_ping/_index.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Service Ping development guidelines +--- diff --git a/doc-locale/ja-jp/development/internal_analytics/service_ping/troubleshooting.md b/doc-locale/ja-jp/development/internal_analytics/service_ping/troubleshooting.md new file mode 100644 index 00000000000..2a518e7726c --- /dev/null +++ b/doc-locale/ja-jp/development/internal_analytics/service_ping/troubleshooting.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Analytics Instrumentation +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. +title: Troubleshooting Service Ping +--- diff --git a/doc-locale/ja-jp/development/internal_api/_index.md b/doc-locale/ja-jp/development/internal_api/_index.md new file mode 100644 index 00000000000..56fa0f8550d --- /dev/null +++ b/doc-locale/ja-jp/development/internal_api/_index.md @@ -0,0 +1,6 @@ +--- +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 +title: Internal API +--- diff --git a/doc-locale/ja-jp/development/internal_api/gitlab_subscriptions.md b/doc-locale/ja-jp/development/internal_api/gitlab_subscriptions.md new file mode 100644 index 00000000000..fd5e33cfefe --- /dev/null +++ b/doc-locale/ja-jp/development/internal_api/gitlab_subscriptions.md @@ -0,0 +1,6 @@ +--- +stage: Fulfillment +group: Provision +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 +title: GitLab Subscriptions Internal API +--- diff --git a/doc-locale/ja-jp/development/internal_api/internal_api_allowed.md b/doc-locale/ja-jp/development/internal_api/internal_api_allowed.md new file mode 100644 index 00000000000..c59aba1bb95 --- /dev/null +++ b/doc-locale/ja-jp/development/internal_api/internal_api_allowed.md @@ -0,0 +1,6 @@ +--- +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 +title: Internal allowed API +--- diff --git a/doc-locale/ja-jp/development/issuable-like-models.md b/doc-locale/ja-jp/development/issuable-like-models.md new file mode 100644 index 00000000000..4516a8b38a9 --- /dev/null +++ b/doc-locale/ja-jp/development/issuable-like-models.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Project Management +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +title: Issuable-like Rails models utilities +--- diff --git a/doc-locale/ja-jp/development/issue_types.md b/doc-locale/ja-jp/development/issue_types.md new file mode 100644 index 00000000000..942169fe8fa --- /dev/null +++ b/doc-locale/ja-jp/development/issue_types.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Project Management +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. +title: Issue Types (deprecated) +--- diff --git a/doc-locale/ja-jp/development/jh_features_review.md b/doc-locale/ja-jp/development/jh_features_review.md new file mode 100644 index 00000000000..2bb719d8926 --- /dev/null +++ b/doc-locale/ja-jp/development/jh_features_review.md @@ -0,0 +1,6 @@ +--- +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. +title: Guidelines for reviewing JiHu (JH) Edition related merge requests +--- diff --git a/doc-locale/ja-jp/development/json.md b/doc-locale/ja-jp/development/json.md new file mode 100644 index 00000000000..e1a32a434a8 --- /dev/null +++ b/doc-locale/ja-jp/development/json.md @@ -0,0 +1,6 @@ +--- +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. +title: JSON development guidelines +--- diff --git a/doc-locale/ja-jp/development/kubernetes.md b/doc-locale/ja-jp/development/kubernetes.md new file mode 100644 index 00000000000..7ab2986aad8 --- /dev/null +++ b/doc-locale/ja-jp/development/kubernetes.md @@ -0,0 +1,6 @@ +--- +stage: Deploy +group: Environments +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. +title: Kubernetes integration development guidelines +--- diff --git a/doc-locale/ja-jp/development/labels/_index.md b/doc-locale/ja-jp/development/labels/_index.md new file mode 100644 index 00000000000..db47e055244 --- /dev/null +++ b/doc-locale/ja-jp/development/labels/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Labels +--- diff --git a/doc-locale/ja-jp/development/lfs.md b/doc-locale/ja-jp/development/lfs.md new file mode 100644 index 00000000000..d8780177982 --- /dev/null +++ b/doc-locale/ja-jp/development/lfs.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Git LFS development guidelines +--- diff --git a/doc-locale/ja-jp/development/licensing.md b/doc-locale/ja-jp/development/licensing.md new file mode 100644 index 00000000000..caf2385c941 --- /dev/null +++ b/doc-locale/ja-jp/development/licensing.md @@ -0,0 +1,6 @@ +--- +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. +title: GitLab Licensing and Compatibility +--- diff --git a/doc-locale/ja-jp/development/logging.md b/doc-locale/ja-jp/development/logging.md new file mode 100644 index 00000000000..0365e79b86b --- /dev/null +++ b/doc-locale/ja-jp/development/logging.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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. +title: Logging development guidelines +--- diff --git a/doc-locale/ja-jp/development/logs.md b/doc-locale/ja-jp/development/logs.md new file mode 100644 index 00000000000..27549c9366b --- /dev/null +++ b/doc-locale/ja-jp/development/logs.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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 +title: Logs +--- diff --git a/doc-locale/ja-jp/development/maintenance_mode.md b/doc-locale/ja-jp/development/maintenance_mode.md new file mode 100644 index 00000000000..0cd95acc2da --- /dev/null +++ b/doc-locale/ja-jp/development/maintenance_mode.md @@ -0,0 +1,6 @@ +--- +stage: Tenant Scale +group: Geo +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. +title: Internal workings of GitLab Maintenance Mode +--- diff --git a/doc-locale/ja-jp/development/mass_insert.md b/doc-locale/ja-jp/development/mass_insert.md new file mode 100644 index 00000000000..2eb32b53199 --- /dev/null +++ b/doc-locale/ja-jp/development/mass_insert.md @@ -0,0 +1,6 @@ +--- +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. +title: Mass inserting Rails models +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/_index.md b/doc-locale/ja-jp/development/merge_request_concepts/_index.md new file mode 100644 index 00000000000..9d49ab92be3 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/_index.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer information explaining terminology and features used in merge requests. +title: Merge request concepts +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/approval_rules.md b/doc-locale/ja-jp/development/merge_request_concepts/approval_rules.md new file mode 100644 index 00000000000..27ee4128123 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/approval_rules.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer documentation explaining the design and workflow of merge request approval rules. +title: Approval rules development guidelines +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/diffs/_index.md b/doc-locale/ja-jp/development/merge_request_concepts/diffs/_index.md new file mode 100644 index 00000000000..bc9dc674bf2 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/diffs/_index.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer documentation for how diffs are generated and rendered in GitLab. +title: Working with diffs +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/diffs/development.md b/doc-locale/ja-jp/development/merge_request_concepts/diffs/development.md new file mode 100644 index 00000000000..296d6670f70 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/diffs/development.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer documentation for the backend design and flow of merge request diffs. +title: Merge request diffs development guide +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/diffs/frontend.md b/doc-locale/ja-jp/development/merge_request_concepts/diffs/frontend.md new file mode 100644 index 00000000000..08598aa7c50 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/diffs/frontend.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer documentation explaining how the different parts of the Vue-based frontend diffs are generated. +title: Merge request diffs frontend overview +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/keep_around_refs.md b/doc-locale/ja-jp/development/merge_request_concepts/keep_around_refs.md new file mode 100644 index 00000000000..591b35981a2 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/keep_around_refs.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Code Review +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. +title: Keep-around ref usage guidelines +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/mergeability_framework.md b/doc-locale/ja-jp/development/merge_request_concepts/mergeability_framework.md new file mode 100644 index 00000000000..6858addfcca --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/mergeability_framework.md @@ -0,0 +1,7 @@ +--- +stage: Create +group: Code Review +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +description: Developer information explaining the process to add a new mergeability check +title: Mergeability framework +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/performance.md b/doc-locale/ja-jp/development/merge_request_concepts/performance.md new file mode 100644 index 00000000000..4099edfa8f3 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/performance.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: Merge Request Performance Guidelines +--- diff --git a/doc-locale/ja-jp/development/merge_request_concepts/rate_limits.md b/doc-locale/ja-jp/development/merge_request_concepts/rate_limits.md new file mode 100644 index 00000000000..9e65c5d7dc4 --- /dev/null +++ b/doc-locale/ja-jp/development/merge_request_concepts/rate_limits.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +title: Application and rate limit guidelines +--- diff --git a/doc-locale/ja-jp/development/metrics.md b/doc-locale/ja-jp/development/metrics.md new file mode 100644 index 00000000000..b43cc4931ad --- /dev/null +++ b/doc-locale/ja-jp/development/metrics.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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 +title: Metrics +--- diff --git a/doc-locale/ja-jp/development/migration_style_guide.md b/doc-locale/ja-jp/development/migration_style_guide.md new file mode 100644 index 00000000000..33b55b6137c --- /dev/null +++ b/doc-locale/ja-jp/development/migration_style_guide.md @@ -0,0 +1,6 @@ +--- +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. +title: Migration Style Guide +--- diff --git a/doc-locale/ja-jp/development/module_with_instance_variables.md b/doc-locale/ja-jp/development/module_with_instance_variables.md new file mode 100644 index 00000000000..5fcdf54cc98 --- /dev/null +++ b/doc-locale/ja-jp/development/module_with_instance_variables.md @@ -0,0 +1,6 @@ +--- +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. +title: Modules with instance variables could be considered harmful +--- diff --git a/doc-locale/ja-jp/development/multi_version_compatibility.md b/doc-locale/ja-jp/development/multi_version_compatibility.md new file mode 100644 index 00000000000..4d49b0dcc6e --- /dev/null +++ b/doc-locale/ja-jp/development/multi_version_compatibility.md @@ -0,0 +1,6 @@ +--- +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. +title: Backwards compatibility across updates +--- diff --git a/doc-locale/ja-jp/development/namespaces.md b/doc-locale/ja-jp/development/namespaces.md new file mode 100644 index 00000000000..541cee9ff4d --- /dev/null +++ b/doc-locale/ja-jp/development/namespaces.md @@ -0,0 +1,6 @@ +--- +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. +title: Namespaces +--- diff --git a/doc-locale/ja-jp/development/navigation_sidebar.md b/doc-locale/ja-jp/development/navigation_sidebar.md new file mode 100644 index 00000000000..a149a379236 --- /dev/null +++ b/doc-locale/ja-jp/development/navigation_sidebar.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Personal Productivity +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. +title: Navigation sidebar +--- diff --git a/doc-locale/ja-jp/development/npmjs.md b/doc-locale/ja-jp/development/npmjs.md new file mode 100644 index 00000000000..dc42e681242 --- /dev/null +++ b/doc-locale/ja-jp/development/npmjs.md @@ -0,0 +1,6 @@ +--- +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. +title: npm package publishing guidelines +--- diff --git a/doc-locale/ja-jp/development/observability/_index.md b/doc-locale/ja-jp/development/observability/_index.md new file mode 100644 index 00000000000..a8558e7aa12 --- /dev/null +++ b/doc-locale/ja-jp/development/observability/_index.md @@ -0,0 +1,7 @@ +--- +stage: Monitor +group: Platform Insights +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: Documentation for developers interested in contributing features or bugfixes for GitLab Observability. +title: GitLab Observability development guidelines +--- diff --git a/doc-locale/ja-jp/development/omnibus.md b/doc-locale/ja-jp/development/omnibus.md new file mode 100644 index 00000000000..c464169e75c --- /dev/null +++ b/doc-locale/ja-jp/development/omnibus.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Distribution +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. +title: What you should know about Omnibus packages +--- diff --git a/doc-locale/ja-jp/development/organization/_index.md b/doc-locale/ja-jp/development/organization/_index.md new file mode 100644 index 00000000000..7d1e36af9e3 --- /dev/null +++ b/doc-locale/ja-jp/development/organization/_index.md @@ -0,0 +1,7 @@ +--- +stage: Tenant Scale +group: Organizations +info: 'See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines' +description: 'Development Guidelines: learn about organization when developing GitLab.' +title: Organization +--- diff --git a/doc-locale/ja-jp/development/packages/_index.md b/doc-locale/ja-jp/development/packages/_index.md new file mode 100644 index 00000000000..11052724ce1 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/_index.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Package Registry +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. +title: Package and container registry development guidelines +--- diff --git a/doc-locale/ja-jp/development/packages/cleanup_policies.md b/doc-locale/ja-jp/development/packages/cleanup_policies.md new file mode 100644 index 00000000000..f7a895c0ee7 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/cleanup_policies.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Container Registry +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. +title: Cleanup policies +--- diff --git a/doc-locale/ja-jp/development/packages/debian_repository.md b/doc-locale/ja-jp/development/packages/debian_repository.md new file mode 100644 index 00000000000..b4f9a816de8 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/debian_repository.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Package Registry +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. +title: Debian Repository +--- diff --git a/doc-locale/ja-jp/development/packages/dependency_proxy.md b/doc-locale/ja-jp/development/packages/dependency_proxy.md new file mode 100644 index 00000000000..6c7dfba10e4 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/dependency_proxy.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Container Registry +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. +title: Dependency Proxy +--- diff --git a/doc-locale/ja-jp/development/packages/harbor_registry_development.md b/doc-locale/ja-jp/development/packages/harbor_registry_development.md new file mode 100644 index 00000000000..4ed73134538 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/harbor_registry_development.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Container Registry +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. +title: Harbor registry +--- diff --git a/doc-locale/ja-jp/development/packages/new_format_development.md b/doc-locale/ja-jp/development/packages/new_format_development.md new file mode 100644 index 00000000000..0fb94a6295d --- /dev/null +++ b/doc-locale/ja-jp/development/packages/new_format_development.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Package Registry +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. +title: Developing support for a new package format +--- diff --git a/doc-locale/ja-jp/development/packages/settings.md b/doc-locale/ja-jp/development/packages/settings.md new file mode 100644 index 00000000000..ed882655903 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/settings.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Package Registry +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. +title: Package Settings +--- diff --git a/doc-locale/ja-jp/development/packages/structure.md b/doc-locale/ja-jp/development/packages/structure.md new file mode 100644 index 00000000000..cd4d6f20e32 --- /dev/null +++ b/doc-locale/ja-jp/development/packages/structure.md @@ -0,0 +1,6 @@ +--- +stage: Package +group: Package Registry +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. +title: Package Structure +--- diff --git a/doc-locale/ja-jp/development/pages/_index.md b/doc-locale/ja-jp/development/pages/_index.md new file mode 100644 index 00000000000..e58819bed31 --- /dev/null +++ b/doc-locale/ja-jp/development/pages/_index.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: Development guidelines for GitLab Pages +title: Contribute to GitLab Pages development +--- diff --git a/doc-locale/ja-jp/development/pages/dnsmasq.md b/doc-locale/ja-jp/development/pages/dnsmasq.md new file mode 100644 index 00000000000..2435544c4f7 --- /dev/null +++ b/doc-locale/ja-jp/development/pages/dnsmasq.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: dnsmasq configuration guidelines for GitLab Pages +title: Using `dnsmasq` to dynamically handle GitLab Pages subdomains +--- diff --git a/doc-locale/ja-jp/development/performance.md b/doc-locale/ja-jp/development/performance.md new file mode 100644 index 00000000000..eed1e2c0263 --- /dev/null +++ b/doc-locale/ja-jp/development/performance.md @@ -0,0 +1,6 @@ +--- +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. +title: Performance Guidelines +--- diff --git a/doc-locale/ja-jp/development/permissions.md b/doc-locale/ja-jp/development/permissions.md new file mode 100644 index 00000000000..02d38d58862 --- /dev/null +++ b/doc-locale/ja-jp/development/permissions.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Permission development guidelines +--- diff --git a/doc-locale/ja-jp/development/permissions/authorizations.md b/doc-locale/ja-jp/development/permissions/authorizations.md new file mode 100644 index 00000000000..39b6a619986 --- /dev/null +++ b/doc-locale/ja-jp/development/permissions/authorizations.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Authorization +--- diff --git a/doc-locale/ja-jp/development/permissions/conventions.md b/doc-locale/ja-jp/development/permissions/conventions.md new file mode 100644 index 00000000000..254f2e336b7 --- /dev/null +++ b/doc-locale/ja-jp/development/permissions/conventions.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Permissions Conventions +--- diff --git a/doc-locale/ja-jp/development/permissions/custom_roles.md b/doc-locale/ja-jp/development/permissions/custom_roles.md new file mode 100644 index 00000000000..abb67bce033 --- /dev/null +++ b/doc-locale/ja-jp/development/permissions/custom_roles.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Custom role development guidelines +--- diff --git a/doc-locale/ja-jp/development/permissions/predefined_roles.md b/doc-locale/ja-jp/development/permissions/predefined_roles.md new file mode 100644 index 00000000000..f2bad6721d0 --- /dev/null +++ b/doc-locale/ja-jp/development/permissions/predefined_roles.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Predefined system of user roles +--- diff --git a/doc-locale/ja-jp/development/pipelines/_index.md b/doc-locale/ja-jp/development/pipelines/_index.md new file mode 100644 index 00000000000..358cde24017 --- /dev/null +++ b/doc-locale/ja-jp/development/pipelines/_index.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Engineering Productivity +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. +title: Pipelines for the GitLab project +--- diff --git a/doc-locale/ja-jp/development/pipelines/internals.md b/doc-locale/ja-jp/development/pipelines/internals.md new file mode 100644 index 00000000000..53dfea4d6b2 --- /dev/null +++ b/doc-locale/ja-jp/development/pipelines/internals.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Engineering Productivity +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. +title: CI configuration internals +--- diff --git a/doc-locale/ja-jp/development/pipelines/performance.md b/doc-locale/ja-jp/development/pipelines/performance.md new file mode 100644 index 00000000000..d0689472928 --- /dev/null +++ b/doc-locale/ja-jp/development/pipelines/performance.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Engineering Productivity +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. +title: CI configuration performance +--- diff --git a/doc-locale/ja-jp/development/policies.md b/doc-locale/ja-jp/development/policies.md new file mode 100644 index 00000000000..0f6b37dfba6 --- /dev/null +++ b/doc-locale/ja-jp/development/policies.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authentication +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. +title: The `DeclarativePolicy` framework +--- diff --git a/doc-locale/ja-jp/development/polling.md b/doc-locale/ja-jp/development/polling.md new file mode 100644 index 00000000000..b79235aae1a --- /dev/null +++ b/doc-locale/ja-jp/development/polling.md @@ -0,0 +1,6 @@ +--- +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. +title: Polling with ETag caching +--- diff --git a/doc-locale/ja-jp/development/product_qualified_lead_guide/_index.md b/doc-locale/ja-jp/development/product_qualified_lead_guide/_index.md new file mode 100644 index 00000000000..2d0d400d5ed --- /dev/null +++ b/doc-locale/ja-jp/development/product_qualified_lead_guide/_index.md @@ -0,0 +1,6 @@ +--- +stage: Growth +group: Acquisition +info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/development/development_processes/#development-guidelines-review. +title: Product Qualified Lead (PQL) development guidelines +--- diff --git a/doc-locale/ja-jp/development/profiling.md b/doc-locale/ja-jp/development/profiling.md new file mode 100644 index 00000000000..a9eec3b7a54 --- /dev/null +++ b/doc-locale/ja-jp/development/profiling.md @@ -0,0 +1,6 @@ +--- +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. +title: Profiling +--- diff --git a/doc-locale/ja-jp/development/project_templates/_index.md b/doc-locale/ja-jp/development/project_templates/_index.md new file mode 100644 index 00000000000..1c5b3e625ef --- /dev/null +++ b/doc-locale/ja-jp/development/project_templates/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Custom group-level project templates development guidelines +--- diff --git a/doc-locale/ja-jp/development/project_templates/add_new_template.md b/doc-locale/ja-jp/development/project_templates/add_new_template.md new file mode 100644 index 00000000000..8f640fbac4f --- /dev/null +++ b/doc-locale/ja-jp/development/project_templates/add_new_template.md @@ -0,0 +1,6 @@ +--- +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 +title: Contribute to built-in project templates +--- diff --git a/doc-locale/ja-jp/development/projections.md b/doc-locale/ja-jp/development/projections.md new file mode 100644 index 00000000000..92417454ebc --- /dev/null +++ b/doc-locale/ja-jp/development/projections.md @@ -0,0 +1,6 @@ +--- +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. +title: Projections +--- diff --git a/doc-locale/ja-jp/development/prometheus_metrics.md b/doc-locale/ja-jp/development/prometheus_metrics.md new file mode 100644 index 00000000000..9ec24c3a4bd --- /dev/null +++ b/doc-locale/ja-jp/development/prometheus_metrics.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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. +title: GitLab Prometheus metrics development guidelines +--- diff --git a/doc-locale/ja-jp/development/pry_debugging.md b/doc-locale/ja-jp/development/pry_debugging.md new file mode 100644 index 00000000000..b1c4a38607c --- /dev/null +++ b/doc-locale/ja-jp/development/pry_debugging.md @@ -0,0 +1,6 @@ +--- +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. +title: Pry debugging +--- diff --git a/doc-locale/ja-jp/development/push_rules/_index.md b/doc-locale/ja-jp/development/push_rules/_index.md new file mode 100644 index 00000000000..ccf0b9638a5 --- /dev/null +++ b/doc-locale/ja-jp/development/push_rules/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Push rules development guidelines +--- diff --git a/doc-locale/ja-jp/development/python_guide/_index.md b/doc-locale/ja-jp/development/python_guide/_index.md new file mode 100644 index 00000000000..101caf17e98 --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Python development guidelines +--- diff --git a/doc-locale/ja-jp/development/python_guide/create_project.md b/doc-locale/ja-jp/development/python_guide/create_project.md new file mode 100644 index 00000000000..c979e9b6291 --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/create_project.md @@ -0,0 +1,6 @@ +--- +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. +title: Create a new python projects +--- diff --git a/doc-locale/ja-jp/development/python_guide/deployment.md b/doc-locale/ja-jp/development/python_guide/deployment.md new file mode 100644 index 00000000000..bd404ee40e5 --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/deployment.md @@ -0,0 +1,6 @@ +--- +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. +title: Deploying Python repositories +--- diff --git a/doc-locale/ja-jp/development/python_guide/getting_started.md b/doc-locale/ja-jp/development/python_guide/getting_started.md new file mode 100644 index 00000000000..714e161fdeb --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/getting_started.md @@ -0,0 +1,6 @@ +--- +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. +title: Getting Started with Python in GitLab +--- diff --git a/doc-locale/ja-jp/development/python_guide/maintainership.md b/doc-locale/ja-jp/development/python_guide/maintainership.md new file mode 100644 index 00000000000..b3ddbf2803f --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/maintainership.md @@ -0,0 +1,6 @@ +--- +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. +title: Python Merge Requests Guidelines +--- diff --git a/doc-locale/ja-jp/development/python_guide/monorepo.md b/doc-locale/ja-jp/development/python_guide/monorepo.md new file mode 100644 index 00000000000..e63f9431d71 --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/monorepo.md @@ -0,0 +1,6 @@ +--- +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. +title: Python as part of the Monorepo +--- diff --git a/doc-locale/ja-jp/development/python_guide/styleguide.md b/doc-locale/ja-jp/development/python_guide/styleguide.md new file mode 100644 index 00000000000..0ee50516dab --- /dev/null +++ b/doc-locale/ja-jp/development/python_guide/styleguide.md @@ -0,0 +1,6 @@ +--- +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. +title: Python style guide +--- diff --git a/doc-locale/ja-jp/development/rails_endpoints/_index.md b/doc-locale/ja-jp/development/rails_endpoints/_index.md new file mode 100644 index 00000000000..81203cb34be --- /dev/null +++ b/doc-locale/ja-jp/development/rails_endpoints/_index.md @@ -0,0 +1,6 @@ +--- +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 +title: Rails Endpoints +--- diff --git a/doc-locale/ja-jp/development/rails_initializers.md b/doc-locale/ja-jp/development/rails_initializers.md new file mode 100644 index 00000000000..6faa8611e24 --- /dev/null +++ b/doc-locale/ja-jp/development/rails_initializers.md @@ -0,0 +1,6 @@ +--- +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. +title: Rails initializers +--- diff --git a/doc-locale/ja-jp/development/rails_update.md b/doc-locale/ja-jp/development/rails_update.md new file mode 100644 index 00000000000..ea42bd7f1f6 --- /dev/null +++ b/doc-locale/ja-jp/development/rails_update.md @@ -0,0 +1,6 @@ +--- +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. +title: Rails upgrade guidelines +--- diff --git a/doc-locale/ja-jp/development/rake_tasks.md b/doc-locale/ja-jp/development/rake_tasks.md new file mode 100644 index 00000000000..35fae053762 --- /dev/null +++ b/doc-locale/ja-jp/development/rake_tasks.md @@ -0,0 +1,6 @@ +--- +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. +title: Rake tasks for developers +--- diff --git a/doc-locale/ja-jp/development/reactive_caching.md b/doc-locale/ja-jp/development/reactive_caching.md new file mode 100644 index 00000000000..e8c567f0ce5 --- /dev/null +++ b/doc-locale/ja-jp/development/reactive_caching.md @@ -0,0 +1,6 @@ +--- +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. +title: Using `ReactiveCaching` +--- diff --git a/doc-locale/ja-jp/development/real_time.md b/doc-locale/ja-jp/development/real_time.md new file mode 100644 index 00000000000..883c327ecc9 --- /dev/null +++ b/doc-locale/ja-jp/development/real_time.md @@ -0,0 +1,6 @@ +--- +stage: Systems +group: Cloud Connector +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. +title: Build and deploy real-time view components +--- diff --git a/doc-locale/ja-jp/development/redis.md b/doc-locale/ja-jp/development/redis.md new file mode 100644 index 00000000000..6026bd65b49 --- /dev/null +++ b/doc-locale/ja-jp/development/redis.md @@ -0,0 +1,6 @@ +--- +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. +title: Redis development guidelines +--- diff --git a/doc-locale/ja-jp/development/redis/new_redis_instance.md b/doc-locale/ja-jp/development/redis/new_redis_instance.md new file mode 100644 index 00000000000..9adcb45a8a4 --- /dev/null +++ b/doc-locale/ja-jp/development/redis/new_redis_instance.md @@ -0,0 +1,6 @@ +--- +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. +title: Add a new Redis instance +--- diff --git a/doc-locale/ja-jp/development/refactoring_guide/_index.md b/doc-locale/ja-jp/development/refactoring_guide/_index.md new file mode 100644 index 00000000000..f680c3d8ef5 --- /dev/null +++ b/doc-locale/ja-jp/development/refactoring_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Refactoring guide +--- diff --git a/doc-locale/ja-jp/development/remote_development/_index.md b/doc-locale/ja-jp/development/remote_development/_index.md new file mode 100644 index 00000000000..e824e88b4a0 --- /dev/null +++ b/doc-locale/ja-jp/development/remote_development/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Web IDE +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. +title: Remote Development developer guidelines +--- diff --git a/doc-locale/ja-jp/development/renaming_features.md b/doc-locale/ja-jp/development/renaming_features.md new file mode 100644 index 00000000000..322e9b5e9f8 --- /dev/null +++ b/doc-locale/ja-jp/development/renaming_features.md @@ -0,0 +1,6 @@ +--- +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. +title: Renaming features +--- diff --git a/doc-locale/ja-jp/development/repository_mirroring.md b/doc-locale/ja-jp/development/repository_mirroring.md new file mode 100644 index 00000000000..263883ddac1 --- /dev/null +++ b/doc-locale/ja-jp/development/repository_mirroring.md @@ -0,0 +1,6 @@ +--- +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. +title: Repository mirroring +--- diff --git a/doc-locale/ja-jp/development/repository_storage_moves/_index.md b/doc-locale/ja-jp/development/repository_storage_moves/_index.md new file mode 100644 index 00000000000..7577f079421 --- /dev/null +++ b/doc-locale/ja-jp/development/repository_storage_moves/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Project Repository Storage Moves +--- diff --git a/doc-locale/ja-jp/development/reusing_abstractions.md b/doc-locale/ja-jp/development/reusing_abstractions.md new file mode 100644 index 00000000000..9951b0c0e9d --- /dev/null +++ b/doc-locale/ja-jp/development/reusing_abstractions.md @@ -0,0 +1,6 @@ +--- +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. +title: Guidelines for reusing abstractions +--- diff --git a/doc-locale/ja-jp/development/routing.md b/doc-locale/ja-jp/development/routing.md new file mode 100644 index 00000000000..1b9597080a6 --- /dev/null +++ b/doc-locale/ja-jp/development/routing.md @@ -0,0 +1,6 @@ +--- +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. +title: Routing +--- diff --git a/doc-locale/ja-jp/development/rubocop_development_guide.md b/doc-locale/ja-jp/development/rubocop_development_guide.md new file mode 100644 index 00000000000..51714156e9a --- /dev/null +++ b/doc-locale/ja-jp/development/rubocop_development_guide.md @@ -0,0 +1,6 @@ +--- +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/development/development_processes/#development-guidelines-review. +title: RuboCop rule development guidelines +--- diff --git a/doc-locale/ja-jp/development/ruby3_gotchas.md b/doc-locale/ja-jp/development/ruby3_gotchas.md new file mode 100644 index 00000000000..4b716b472a3 --- /dev/null +++ b/doc-locale/ja-jp/development/ruby3_gotchas.md @@ -0,0 +1,6 @@ +--- +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. +title: Ruby 3 gotchas +--- diff --git a/doc-locale/ja-jp/development/ruby_upgrade.md b/doc-locale/ja-jp/development/ruby_upgrade.md new file mode 100644 index 00000000000..4a1cb060f7a --- /dev/null +++ b/doc-locale/ja-jp/development/ruby_upgrade.md @@ -0,0 +1,6 @@ +--- +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. +title: Ruby upgrade guidelines +--- diff --git a/doc-locale/ja-jp/development/scalability.md b/doc-locale/ja-jp/development/scalability.md new file mode 100644 index 00000000000..b089079b6a7 --- /dev/null +++ b/doc-locale/ja-jp/development/scalability.md @@ -0,0 +1,6 @@ +--- +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. +title: GitLab scalability +--- diff --git a/doc-locale/ja-jp/development/search/advanced_search_migration_styleguide.md b/doc-locale/ja-jp/development/search/advanced_search_migration_styleguide.md new file mode 100644 index 00000000000..22c09b8a305 --- /dev/null +++ b/doc-locale/ja-jp/development/search/advanced_search_migration_styleguide.md @@ -0,0 +1,6 @@ +--- +stage: Foundations +group: Global Search +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. +title: Advanced search migration style guide +--- diff --git a/doc-locale/ja-jp/development/sec/_index.md b/doc-locale/ja-jp/development/sec/_index.md new file mode 100644 index 00000000000..191d93f2ac5 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/_index.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Static Analysis +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. +title: Sec section development guidelines +--- diff --git a/doc-locale/ja-jp/development/sec/analyzer_development_guide.md b/doc-locale/ja-jp/development/sec/analyzer_development_guide.md new file mode 100644 index 00000000000..90ba0f63e16 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/analyzer_development_guide.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Static Analysis +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. +title: Sec section analyzer development +--- diff --git a/doc-locale/ja-jp/development/sec/cyclonedx_property_taxonomy.md b/doc-locale/ja-jp/development/sec/cyclonedx_property_taxonomy.md new file mode 100644 index 00000000000..03a08967ead --- /dev/null +++ b/doc-locale/ja-jp/development/sec/cyclonedx_property_taxonomy.md @@ -0,0 +1,6 @@ +--- +stage: Security Risk Management +group: Security Insights +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 +title: GitLab CycloneDX property taxonomy +--- diff --git a/doc-locale/ja-jp/development/sec/gemnasium_analyzer_data.md b/doc-locale/ja-jp/development/sec/gemnasium_analyzer_data.md new file mode 100644 index 00000000000..3a791668f59 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/gemnasium_analyzer_data.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Composition Analysis +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. +title: Gemnasium analyzer data +--- diff --git a/doc-locale/ja-jp/development/sec/generate_test_vulnerabilities.md b/doc-locale/ja-jp/development/sec/generate_test_vulnerabilities.md new file mode 100644 index 00000000000..e856b41e610 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/generate_test_vulnerabilities.md @@ -0,0 +1,6 @@ +--- +stage: Security Risk Management +group: Security Insights +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. +title: Generate test vulnerabilities +--- diff --git a/doc-locale/ja-jp/development/sec/sbom_dependency_graph_ingestion_overview.md b/doc-locale/ja-jp/development/sec/sbom_dependency_graph_ingestion_overview.md new file mode 100644 index 00000000000..1e2fe3eddd4 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/sbom_dependency_graph_ingestion_overview.md @@ -0,0 +1,6 @@ +--- +stage: Security Risk Management +group: Security Insights +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 +title: SBoM dependency graph ingestion overview +--- diff --git a/doc-locale/ja-jp/development/sec/security_report_ingestion_overview.md b/doc-locale/ja-jp/development/sec/security_report_ingestion_overview.md new file mode 100644 index 00000000000..aedf4d5ab24 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/security_report_ingestion_overview.md @@ -0,0 +1,6 @@ +--- +stage: Security Risk Management +group: Security Insights +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 +title: Security report ingestion overview +--- diff --git a/doc-locale/ja-jp/development/sec/token_revocation_api.md b/doc-locale/ja-jp/development/sec/token_revocation_api.md new file mode 100644 index 00000000000..5ecd600210a --- /dev/null +++ b/doc-locale/ja-jp/development/sec/token_revocation_api.md @@ -0,0 +1,6 @@ +--- +stage: Application Security Testing +group: Static Analysis +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 +title: Token Revocation API +--- diff --git a/doc-locale/ja-jp/development/sec/vulnerability_tracking.md b/doc-locale/ja-jp/development/sec/vulnerability_tracking.md new file mode 100644 index 00000000000..ae9fc97cd38 --- /dev/null +++ b/doc-locale/ja-jp/development/sec/vulnerability_tracking.md @@ -0,0 +1,6 @@ +--- +stage: Security Risk Management +group: Security Insights +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 +title: Vulnerability tracking overview +--- diff --git a/doc-locale/ja-jp/development/secure_coding_guidelines.md b/doc-locale/ja-jp/development/secure_coding_guidelines.md new file mode 100644 index 00000000000..7738ed50c00 --- /dev/null +++ b/doc-locale/ja-jp/development/secure_coding_guidelines.md @@ -0,0 +1,6 @@ +--- +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. +title: Secure coding development guidelines +--- diff --git a/doc-locale/ja-jp/development/semver.md b/doc-locale/ja-jp/development/semver.md new file mode 100644 index 00000000000..6a0dd6dd2f3 --- /dev/null +++ b/doc-locale/ja-jp/development/semver.md @@ -0,0 +1,6 @@ +--- +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. +title: Semantic Versioning of Database Records +--- diff --git a/doc-locale/ja-jp/development/service_measurement.md b/doc-locale/ja-jp/development/service_measurement.md new file mode 100644 index 00000000000..ba311ad3d4d --- /dev/null +++ b/doc-locale/ja-jp/development/service_measurement.md @@ -0,0 +1,6 @@ +--- +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. +title: GitLab Developers Guide to service measurement +--- diff --git a/doc-locale/ja-jp/development/session.md b/doc-locale/ja-jp/development/session.md new file mode 100644 index 00000000000..d3baa8ff11a --- /dev/null +++ b/doc-locale/ja-jp/development/session.md @@ -0,0 +1,6 @@ +--- +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. +title: Accessing session data +--- diff --git a/doc-locale/ja-jp/development/shared_files.md b/doc-locale/ja-jp/development/shared_files.md new file mode 100644 index 00000000000..918e9060b8b --- /dev/null +++ b/doc-locale/ja-jp/development/shared_files.md @@ -0,0 +1,6 @@ +--- +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. +title: Shared files +--- diff --git a/doc-locale/ja-jp/development/shell_commands.md b/doc-locale/ja-jp/development/shell_commands.md new file mode 100644 index 00000000000..aa4ebab6b9e --- /dev/null +++ b/doc-locale/ja-jp/development/shell_commands.md @@ -0,0 +1,6 @@ +--- +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. +title: Shell command development guidelines +--- diff --git a/doc-locale/ja-jp/development/shell_scripting_guide/_index.md b/doc-locale/ja-jp/development/shell_scripting_guide/_index.md new file mode 100644 index 00000000000..db3e233754f --- /dev/null +++ b/doc-locale/ja-jp/development/shell_scripting_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Shell scripting standards and style guidelines +--- diff --git a/doc-locale/ja-jp/development/sidekiq/_index.md b/doc-locale/ja-jp/development/sidekiq/_index.md new file mode 100644 index 00000000000..3fb9772e172 --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq development guidelines +--- diff --git a/doc-locale/ja-jp/development/sidekiq/compatibility_across_updates.md b/doc-locale/ja-jp/development/sidekiq/compatibility_across_updates.md new file mode 100644 index 00000000000..9e21e0080cf --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/compatibility_across_updates.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq Compatibility across Updates +--- diff --git a/doc-locale/ja-jp/development/sidekiq/idempotent_jobs.md b/doc-locale/ja-jp/development/sidekiq/idempotent_jobs.md new file mode 100644 index 00000000000..c6b191450c8 --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/idempotent_jobs.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq idempotent jobs +--- diff --git a/doc-locale/ja-jp/development/sidekiq/limited_capacity_worker.md b/doc-locale/ja-jp/development/sidekiq/limited_capacity_worker.md new file mode 100644 index 00000000000..e7631785fe0 --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/limited_capacity_worker.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq limited capacity worker +--- diff --git a/doc-locale/ja-jp/development/sidekiq/logging.md b/doc-locale/ja-jp/development/sidekiq/logging.md new file mode 100644 index 00000000000..0e8c9db44fd --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/logging.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq logging +--- diff --git a/doc-locale/ja-jp/development/sidekiq/worker_attributes.md b/doc-locale/ja-jp/development/sidekiq/worker_attributes.md new file mode 100644 index 00000000000..7f88aa7cf68 --- /dev/null +++ b/doc-locale/ja-jp/development/sidekiq/worker_attributes.md @@ -0,0 +1,6 @@ +--- +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. +title: Sidekiq worker attributes +--- diff --git a/doc-locale/ja-jp/development/software_design.md b/doc-locale/ja-jp/development/software_design.md new file mode 100644 index 00000000000..fede38a2086 --- /dev/null +++ b/doc-locale/ja-jp/development/software_design.md @@ -0,0 +1,6 @@ +--- +stage: none +group: Engineering Productivity +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. +title: Software design guides +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/_index.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/_index.md new file mode 100644 index 00000000000..f2f4dbcc809 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/_index.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Spam protection and CAPTCHA +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/exploratory_testing.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/exploratory_testing.md new file mode 100644 index 00000000000..1691e888c88 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/exploratory_testing.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Exploratory testing of CAPTCHAs +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/graphql_api.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/graphql_api.md new file mode 100644 index 00000000000..8bc3aa9cf51 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/graphql_api.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: GraphQL API spam protection and CAPTCHA support +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/model_and_services.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/model_and_services.md new file mode 100644 index 00000000000..46c5d24b878 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/model_and_services.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Model and services spam protection and CAPTCHA support +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/rest_api.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/rest_api.md new file mode 100644 index 00000000000..e896a80aea5 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/rest_api.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: REST API spam protection and CAPTCHA support +--- diff --git a/doc-locale/ja-jp/development/spam_protection_and_captcha/web_ui.md b/doc-locale/ja-jp/development/spam_protection_and_captcha/web_ui.md new file mode 100644 index 00000000000..b924e9260d3 --- /dev/null +++ b/doc-locale/ja-jp/development/spam_protection_and_captcha/web_ui.md @@ -0,0 +1,6 @@ +--- +stage: Software Supply Chain Security +group: Authorization +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. +title: Web UI spam protection and CAPTCHA support +--- diff --git a/doc-locale/ja-jp/development/sql.md b/doc-locale/ja-jp/development/sql.md new file mode 100644 index 00000000000..0491c3ffc8c --- /dev/null +++ b/doc-locale/ja-jp/development/sql.md @@ -0,0 +1,6 @@ +--- +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. +title: SQL Query Guidelines +--- diff --git a/doc-locale/ja-jp/development/stage_group_observability/_index.md b/doc-locale/ja-jp/development/stage_group_observability/_index.md new file mode 100644 index 00000000000..e6c12917d0b --- /dev/null +++ b/doc-locale/ja-jp/development/stage_group_observability/_index.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Observability for stage groups +--- diff --git a/doc-locale/ja-jp/development/stage_group_observability/dashboards/_index.md b/doc-locale/ja-jp/development/stage_group_observability/dashboards/_index.md new file mode 100644 index 00000000000..67619441d51 --- /dev/null +++ b/doc-locale/ja-jp/development/stage_group_observability/dashboards/_index.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Dashboards for stage groups +--- diff --git a/doc-locale/ja-jp/development/stage_group_observability/dashboards/error_budget_detail.md b/doc-locale/ja-jp/development/stage_group_observability/dashboards/error_budget_detail.md new file mode 100644 index 00000000000..037efca0acf --- /dev/null +++ b/doc-locale/ja-jp/development/stage_group_observability/dashboards/error_budget_detail.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Error budget detail dashboard +--- diff --git a/doc-locale/ja-jp/development/stage_group_observability/dashboards/stage_group_dashboard.md b/doc-locale/ja-jp/development/stage_group_observability/dashboards/stage_group_dashboard.md new file mode 100644 index 00000000000..9b008f12699 --- /dev/null +++ b/doc-locale/ja-jp/development/stage_group_observability/dashboards/stage_group_dashboard.md @@ -0,0 +1,6 @@ +--- +stage: Platforms +group: Scalability +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. +title: Stage group dashboard +--- diff --git a/doc-locale/ja-jp/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md b/doc-locale/ja-jp/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md new file mode 100644 index 00000000000..b5cb9e890b7 --- /dev/null +++ b/doc-locale/ja-jp/development/stage_group_observability/gitlab_instrumentation_for_opentelemetry.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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. +title: GitLab instrumentation for OpenTelemetry +--- diff --git a/doc-locale/ja-jp/development/testing_guide/_index.md b/doc-locale/ja-jp/development/testing_guide/_index.md new file mode 100644 index 00000000000..bc9b3b8301e --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing standards and style guidelines +--- diff --git a/doc-locale/ja-jp/development/testing_guide/best_practices.md b/doc-locale/ja-jp/development/testing_guide/best_practices.md new file mode 100644 index 00000000000..0885cfa32a7 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/best_practices.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: 'See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines' +description: GitLab development guidelines - testing best practices. +title: Testing best practices +--- diff --git a/doc-locale/ja-jp/development/testing_guide/contract/_index.md b/doc-locale/ja-jp/development/testing_guide/contract/_index.md new file mode 100644 index 00000000000..94000574438 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/contract/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Contract testing +--- diff --git a/doc-locale/ja-jp/development/testing_guide/contract/consumer_tests.md b/doc-locale/ja-jp/development/testing_guide/contract/consumer_tests.md new file mode 100644 index 00000000000..0380f06d150 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/contract/consumer_tests.md @@ -0,0 +1,6 @@ +--- +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. +title: Writing consumer tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/contract/provider_tests.md b/doc-locale/ja-jp/development/testing_guide/contract/provider_tests.md new file mode 100644 index 00000000000..b93c6b4370d --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/contract/provider_tests.md @@ -0,0 +1,6 @@ +--- +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. +title: Writing provider tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/_index.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/_index.md new file mode 100644 index 00000000000..81862ae4b42 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: End-to-end Testing +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/_index.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/_index.md new file mode 100644 index 00000000000..c0178eeccc6 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Beginner's guide to writing end-to-end tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/flows.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/flows.md new file mode 100644 index 00000000000..4f0238fdea9 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/flows.md @@ -0,0 +1,6 @@ +--- +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. +title: Flows in GitLab QA +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/page_objects.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/page_objects.md new file mode 100644 index 00000000000..9ded8b01373 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/page_objects.md @@ -0,0 +1,6 @@ +--- +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. +title: Page objects in GitLab QA +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/resources.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/resources.md new file mode 100644 index 00000000000..dfae6835a0b --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/beginners_guide/resources.md @@ -0,0 +1,6 @@ +--- +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. +title: Resource classes in GitLab QA +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/_index.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/_index.md new file mode 100644 index 00000000000..50d2d488d96 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: End-to-end testing Best Practices +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/dynamic_element_validation.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/dynamic_element_validation.md new file mode 100644 index 00000000000..64443a6f12b --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/dynamic_element_validation.md @@ -0,0 +1,6 @@ +--- +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. +title: Dynamic Element Validation +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/execution_context_selection.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/execution_context_selection.md new file mode 100644 index 00000000000..f98b766eb77 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/execution_context_selection.md @@ -0,0 +1,6 @@ +--- +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. +title: Execution context selection +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/feature_flags.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/feature_flags.md new file mode 100644 index 00000000000..7708c53bd64 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/feature_flags.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing with feature flags +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/rspec_metadata_tests.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/rspec_metadata_tests.md new file mode 100644 index 00000000000..95dadf64bad --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/rspec_metadata_tests.md @@ -0,0 +1,6 @@ +--- +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. +title: RSpec metadata for end-to-end tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/users.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/users.md new file mode 100644 index 00000000000..4d3dd02f647 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/users.md @@ -0,0 +1,6 @@ +--- +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. +title: Environment Setup | Users +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/waits.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/waits.md new file mode 100644 index 00000000000..3db9cf91bc0 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/best_practices/waits.md @@ -0,0 +1,6 @@ +--- +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. +title: Waits +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/debugging_end_to_end_test_failures.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/debugging_end_to_end_test_failures.md new file mode 100644 index 00000000000..a42c2bf9f16 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/debugging_end_to_end_test_failures.md @@ -0,0 +1,4 @@ +--- +title: Debugging Failing Tests and Test Pipelines +description: Guidelines for investigating end-to-end test pipeline failures +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/feature_flag_testing.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/feature_flag_testing.md new file mode 100644 index 00000000000..a980837ce49 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/feature_flag_testing.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing feature flags with end-to-end tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/_index.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/_index.md new file mode 100644 index 00000000000..52d3fd8278b --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Running the tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/running_tests_that_require_special_setup.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/running_tests_that_require_special_setup.md new file mode 100644 index 00000000000..252e4eb9996 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/running_tests/running_tests_that_require_special_setup.md @@ -0,0 +1,6 @@ +--- +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. +title: Running tests that require special setup +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/style_guide.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/style_guide.md new file mode 100644 index 00000000000..7a018dc7377 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/style_guide.md @@ -0,0 +1,6 @@ +--- +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. +title: Style guide for writing end-to-end tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/test_infrastructure.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/test_infrastructure.md new file mode 100644 index 00000000000..2ab610bbe61 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/test_infrastructure.md @@ -0,0 +1,6 @@ +--- +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. +title: End-to-end Testing Infrastructure for Cloud Integrations +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/test_pipelines.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/test_pipelines.md new file mode 100644 index 00000000000..50d243a41af --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/test_pipelines.md @@ -0,0 +1,6 @@ +--- +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. +title: End-to-end test pipelines +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/tips_and_tricks.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/tips_and_tricks.md new file mode 100644 index 00000000000..e490c7079c3 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/tips_and_tricks.md @@ -0,0 +1,4 @@ +--- +title: "Test Governance Tips and Tricks" +description: "This page lists a number of tips and tricks we have found useful in day to day end-to-end test level related tasks." +--- diff --git a/doc-locale/ja-jp/development/testing_guide/end_to_end/troubleshooting.md b/doc-locale/ja-jp/development/testing_guide/end_to_end/troubleshooting.md new file mode 100644 index 00000000000..3200556a040 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/end_to_end/troubleshooting.md @@ -0,0 +1,6 @@ +--- +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. +title: Troubleshooting end-to-end tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/flaky_tests.md b/doc-locale/ja-jp/development/testing_guide/flaky_tests.md new file mode 100644 index 00000000000..fcdf56f16af --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/flaky_tests.md @@ -0,0 +1,6 @@ +--- +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. +title: Flaky tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/frontend_testing.md b/doc-locale/ja-jp/development/testing_guide/frontend_testing.md new file mode 100644 index 00000000000..4bea73db9b5 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/frontend_testing.md @@ -0,0 +1,6 @@ +--- +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. +title: Frontend testing standards and style guidelines +--- diff --git a/doc-locale/ja-jp/development/testing_guide/review_apps.md b/doc-locale/ja-jp/development/testing_guide/review_apps.md new file mode 100644 index 00000000000..3caaa02ea6c --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/review_apps.md @@ -0,0 +1,6 @@ +--- +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. +title: Using review apps in the development of GitLab +--- diff --git a/doc-locale/ja-jp/development/testing_guide/smoke.md b/doc-locale/ja-jp/development/testing_guide/smoke.md new file mode 100644 index 00000000000..ae729f6828c --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/smoke.md @@ -0,0 +1,6 @@ +--- +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. +title: Smoke Tests +--- diff --git a/doc-locale/ja-jp/development/testing_guide/test_results_tracking.md b/doc-locale/ja-jp/development/testing_guide/test_results_tracking.md new file mode 100644 index 00000000000..099aa9079f3 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/test_results_tracking.md @@ -0,0 +1,6 @@ +--- +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. +title: Test results tracking +--- diff --git a/doc-locale/ja-jp/development/testing_guide/testing_levels.md b/doc-locale/ja-jp/development/testing_guide/testing_levels.md new file mode 100644 index 00000000000..bba477f35ae --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/testing_levels.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing levels +--- diff --git a/doc-locale/ja-jp/development/testing_guide/testing_migrations_guide.md b/doc-locale/ja-jp/development/testing_guide/testing_migrations_guide.md new file mode 100644 index 00000000000..be19f772e5d --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/testing_migrations_guide.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing Rails migrations at GitLab +--- diff --git a/doc-locale/ja-jp/development/testing_guide/testing_rake_tasks.md b/doc-locale/ja-jp/development/testing_guide/testing_rake_tasks.md new file mode 100644 index 00000000000..1ff8e3cec1f --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/testing_rake_tasks.md @@ -0,0 +1,6 @@ +--- +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. +title: Testing Rake tasks +--- diff --git a/doc-locale/ja-jp/development/testing_guide/testing_vue3.md b/doc-locale/ja-jp/development/testing_guide/testing_vue3.md new file mode 100644 index 00000000000..806b51c00e8 --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/testing_vue3.md @@ -0,0 +1,6 @@ +--- +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. +title: Vue 3 Testing +--- diff --git a/doc-locale/ja-jp/development/testing_guide/unhealthy_tests.md b/doc-locale/ja-jp/development/testing_guide/unhealthy_tests.md new file mode 100644 index 00000000000..f68682f696c --- /dev/null +++ b/doc-locale/ja-jp/development/testing_guide/unhealthy_tests.md @@ -0,0 +1,7 @@ +--- +stage: none +group: unassigned +info: 'See the Technical Writers assigned to Development Guidelines: https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments-to-development-guidelines' +description: GitLab development guidelines - Unhealthy tests. +title: Unhealthy tests +--- diff --git a/doc-locale/ja-jp/development/token_authenticatable.md b/doc-locale/ja-jp/development/token_authenticatable.md new file mode 100644 index 00000000000..d54150c0835 --- /dev/null +++ b/doc-locale/ja-jp/development/token_authenticatable.md @@ -0,0 +1,6 @@ +--- +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. +title: Using the `TokenAuthenticatable` concern +--- diff --git a/doc-locale/ja-jp/development/tracing.md b/doc-locale/ja-jp/development/tracing.md new file mode 100644 index 00000000000..8ade39d1d9d --- /dev/null +++ b/doc-locale/ja-jp/development/tracing.md @@ -0,0 +1,6 @@ +--- +stage: Monitor +group: Platform Insights +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 +title: Distributed tracing +--- diff --git a/doc-locale/ja-jp/development/transient/prevention-patterns.md b/doc-locale/ja-jp/development/transient/prevention-patterns.md new file mode 100644 index 00000000000..62041dfc08a --- /dev/null +++ b/doc-locale/ja-jp/development/transient/prevention-patterns.md @@ -0,0 +1,6 @@ +--- +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. +title: Preventing Transient Bugs +--- diff --git a/doc-locale/ja-jp/development/uploads/_index.md b/doc-locale/ja-jp/development/uploads/_index.md new file mode 100644 index 00000000000..ad6326c1e5b --- /dev/null +++ b/doc-locale/ja-jp/development/uploads/_index.md @@ -0,0 +1,6 @@ +--- +stage: SaaS Platforms +group: Scalability +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. +title: Uploads development guidelines +--- diff --git a/doc-locale/ja-jp/development/uploads/working_with_uploads.md b/doc-locale/ja-jp/development/uploads/working_with_uploads.md new file mode 100644 index 00000000000..229a8413259 --- /dev/null +++ b/doc-locale/ja-jp/development/uploads/working_with_uploads.md @@ -0,0 +1,6 @@ +--- +stage: SaaS Platforms +group: Scalability +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. +title: 'Uploads guide: Adding new uploads' +--- diff --git a/doc-locale/ja-jp/development/utilities.md b/doc-locale/ja-jp/development/utilities.md new file mode 100644 index 00000000000..3d0c673b164 --- /dev/null +++ b/doc-locale/ja-jp/development/utilities.md @@ -0,0 +1,6 @@ +--- +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. +title: GitLab utilities +--- diff --git a/doc-locale/ja-jp/development/ux/_index.md b/doc-locale/ja-jp/development/ux/_index.md new file mode 100644 index 00000000000..f440e16b887 --- /dev/null +++ b/doc-locale/ja-jp/development/ux/_index.md @@ -0,0 +1,6 @@ +--- +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. +title: Contribute to UX design +--- diff --git a/doc-locale/ja-jp/development/value_stream_analytics.md b/doc-locale/ja-jp/development/value_stream_analytics.md new file mode 100644 index 00000000000..3a1d5cb39dd --- /dev/null +++ b/doc-locale/ja-jp/development/value_stream_analytics.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Optimize +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. +title: Value stream analytics development guidelines +--- diff --git a/doc-locale/ja-jp/development/value_stream_analytics/value_stream_analytics_aggregated_backend.md b/doc-locale/ja-jp/development/value_stream_analytics/value_stream_analytics_aggregated_backend.md new file mode 100644 index 00000000000..bae36e324e0 --- /dev/null +++ b/doc-locale/ja-jp/development/value_stream_analytics/value_stream_analytics_aggregated_backend.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Optimize +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. +title: Aggregated Value Stream Analytics +--- diff --git a/doc-locale/ja-jp/development/vs_code_debugging.md b/doc-locale/ja-jp/development/vs_code_debugging.md new file mode 100644 index 00000000000..ee9f1b15815 --- /dev/null +++ b/doc-locale/ja-jp/development/vs_code_debugging.md @@ -0,0 +1,6 @@ +--- +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. +title: VS Code debugging +--- diff --git a/doc-locale/ja-jp/development/webhooks.md b/doc-locale/ja-jp/development/webhooks.md new file mode 100644 index 00000000000..5c67bbf8a20 --- /dev/null +++ b/doc-locale/ja-jp/development/webhooks.md @@ -0,0 +1,7 @@ +--- +stage: Foundations +group: Import and Integrate +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: Development guidelines for webhooks +title: Webhooks developer guide +--- diff --git a/doc-locale/ja-jp/development/wikis.md b/doc-locale/ja-jp/development/wikis.md new file mode 100644 index 00000000000..11b8e2d0413 --- /dev/null +++ b/doc-locale/ja-jp/development/wikis.md @@ -0,0 +1,7 @@ +--- +stage: Plan +group: Knowledge +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: Development guidelines for Wikis +title: Wikis development guidelines +--- diff --git a/doc-locale/ja-jp/development/work_items.md b/doc-locale/ja-jp/development/work_items.md new file mode 100644 index 00000000000..3da9996b6fe --- /dev/null +++ b/doc-locale/ja-jp/development/work_items.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Project Management +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. +title: Work items and work item types +--- diff --git a/doc-locale/ja-jp/development/work_items_widgets.md b/doc-locale/ja-jp/development/work_items_widgets.md new file mode 100644 index 00000000000..ce9d944cb73 --- /dev/null +++ b/doc-locale/ja-jp/development/work_items_widgets.md @@ -0,0 +1,6 @@ +--- +stage: Plan +group: Project Management +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. +title: Work items widgets +--- diff --git a/doc-locale/ja-jp/development/workhorse/_index.md b/doc-locale/ja-jp/development/workhorse/_index.md new file mode 100644 index 00000000000..1846000fcf8 --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/_index.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: GitLab Workhorse +--- diff --git a/doc-locale/ja-jp/development/workhorse/channel.md b/doc-locale/ja-jp/development/workhorse/channel.md new file mode 100644 index 00000000000..f80ded5e07b --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/channel.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Websocket channel support for Workhorse +--- diff --git a/doc-locale/ja-jp/development/workhorse/configuration.md b/doc-locale/ja-jp/development/workhorse/configuration.md new file mode 100644 index 00000000000..c90ef6e41d1 --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/configuration.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Workhorse configuration +--- diff --git a/doc-locale/ja-jp/development/workhorse/gitlab_features.md b/doc-locale/ja-jp/development/workhorse/gitlab_features.md new file mode 100644 index 00000000000..8215c1dcfff --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/gitlab_features.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Features that rely on Workhorse +--- diff --git a/doc-locale/ja-jp/development/workhorse/handlers.md b/doc-locale/ja-jp/development/workhorse/handlers.md new file mode 100644 index 00000000000..b33764f5a5f --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/handlers.md @@ -0,0 +1,6 @@ +--- +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/engineering/ux/technical-writing/#assignments +title: Workhorse handlers +--- diff --git a/doc-locale/ja-jp/development/workhorse/new_features.md b/doc-locale/ja-jp/development/workhorse/new_features.md new file mode 100644 index 00000000000..13e159aac1f --- /dev/null +++ b/doc-locale/ja-jp/development/workhorse/new_features.md @@ -0,0 +1,6 @@ +--- +stage: Create +group: Source Code +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. +title: Adding new features to Workhorse +--- diff --git a/doc/development/cells/_index.md b/doc/development/cells/_index.md index 81e20afae11..f13ad70f15e 100644 --- a/doc/development/cells/_index.md +++ b/doc/development/cells/_index.md @@ -15,29 +15,13 @@ Below are available schemas related to Cells and Organizations: | ------ | ----------- | | `gitlab_main_cell`| Use for all tables in the `main:` database that are for an Organization. For example, `projects` and `groups` | | `gitlab_main_clusterwide_setting` | All tables in the `main:` database related to Cluster settings. For example, `application_settings`. | -| `gitlab_main_clusterwide` | All tables in the `main:` database where all rows, or a subset of rows needs to be present across the cluster, in the [Cells](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/) architecture. For example, `users`. For the [Cells 1.0 architecture](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/iterations/cells-1.0/), there are no real clusterwide tables as each cell will have its own database. In effect, these tables will still be stored locally in each cell. | +| `gitlab_main_clusterwide` (deprecated) | All tables in the `main:` database where all rows, or a subset of rows needs to be present across the cluster, in the [Cells](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/) architecture. For example, `plans`. For the [Cells 1.0 architecture](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/iterations/cells-1.0/), there are no real clusterwide tables as each cell will have its own database. In effect, these tables will still be stored locally in each cell. | | `gitlab_main_cell_local` | For tables in the `main:` database that are related to features that is distinct for each cell. For example, `zoekt_nodes`, or `shards`. These cell-local tables should not have any foreign key references from/to organization tables. | | `gitlab_ci` | Use for all tables in the `ci:` database that are for an Organization. For example, `ci_pipelines` and `ci_builds` | | `gitlab_ci_cell_local` | For tables in the `ci:` database that are related to features that is distinct for each cell. For example, `instance_type_ci_runners`, or `ci_cost_settings`. These cell-local tables should not have any foreign key references from/to organization tables. | -| `gitlab_main_user` | Schema for all User-related tables, ex. users, etc. Most user functionality is organizational level (e.g. commenting on an issue), but some functionality (e.g. login) is cluster-wide. | +| `gitlab_main_user` | Schema for all User-related tables, ex. `users`, `emails`, etc. Most user functionality is organizational level so should use `gitlab_main_cell` instead (e.g. commenting on an issue).For user functionality that is not organizational level, use this schema. Tables on this schema must strictly belong to a user. | -## Choose either the `gitlab_main_cell` or `gitlab_main_clusterwide` schema - -Depending on the use case, your feature may be [organization-level, or clusterwide](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/#how-do-i-decide-whether-to-move-my-feature-to-the-cluster-cell-or-organization-level) and hence the tables used for the feature should also use the appropriate schema. - -When you choose the appropriate [schema](#available-cells--organization-schemas) for tables, consider the following guidelines as part of the [Cells](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/) architecture: - -- Default to `gitlab_main_cell`: We expect most tables to be assigned to the `gitlab_main_cell` schema by default. Choose this schema if the data in the table is related to `projects` or `namespaces`. -- Consult with the Tenant Scale group: If you believe that the `gitlab_main_clusterwide` schema is more suitable for a table, seek approval from the Tenant Scale group. This is crucial because it has scaling implications and may require reconsideration of the schema choice. - -When proposing new tables with `gitlab_main_clusterwide` schema, be aware of the following: - -- Do not use cluster-wide database tables to store [static data](#static-data). -- Must be able to be synchronized independently to other / all cells. -- Should only have a tiny amount of rows. Larger tables with many rows are not suitable to be cluster-wide tables. -- Must not have references to / from other tables that will cause data issues when synchronized to other cells. - -We may also ask teams to update tables from `gitlab_main_clusterwide` to `gitlab_main_cell` as required, which also might require adding sharding keys to these tables. +Most tables will require a [sharding key](../organization/_index.md#defining-a-sharding-key-for-all-organizational-tables) to be defined. To understand how existing tables are classified, you can use [this dashboard](https://manojmj.gitlab.io/tenant-scale-schema-progress/). @@ -47,252 +31,33 @@ After a schema has been assigned, the merge request pipeline might fail due to o - [Cross-database transactions](../database/multiple_databases.md#fixing-cross-database-transactions) - [Cross-database foreign keys](../database/multiple_databases.md#foreign-keys-that-cross-databases) -## Defining a sharding key for all organizational tables +## What schema to choose if the feature can be cluster-wide? -All tables with the following `gitlab_schema` are considered organization level: +The `gitlab_main_clusterwide` schema is now deprecated. -- `gitlab_main_cell` -- `gitlab_ci` -- `gitlab_sec` -- `gitlab_main_user` +Clusterwide features are +[heavily discouraged](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/#how-do-i-decide-whether-to-move-my-feature-to-the-cluster-cell-or-organization-level), +and there are [no plans to perform any cluster-wide synchronization](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/decisions/014_clusterwide_syncing_in_cells_1_0/). -All newly created organization-level tables are required to have a `sharding_key` -defined in the corresponding `db/docs/` file for that table. +Choose a different schema from the list of available GitLab [schemas](#available-cells--organization-schemas) instead. +We expect most tables to use the `gitlab_main_cell` schema, especially if the +table in the table is related to `projects`, or `namespaces`. -The purpose of the sharding key is documented in the -[Organization isolation blueprint](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/isolation/), -but in short this column is used to provide a standard way of determining which -Organization owns a particular row in the database. The column will be used in -the future to enforce constraints on data not cross Organization boundaries. It -will also be used in the future to provide a uniform way to migrate data -between Cells. +Consult with the [Tenant Scale group](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/tenant-scale/): +If you believe that the `gitlab_main_clusterwide` schema is more suitable for a +table, seek approval from the Tenant Scale group. Here are some considerations +to think about: -The actual name of the foreign key can be anything but it must reference a row -in `projects` or `groups`. The chosen `sharding_key` column must be non-nullable. +- The related feature must work on multiple cells, not just the legacy cell. +- How would the related feature scale across many Organizations and Cells ? +- The underlying data must be consistent on different cells. + For example, do not use cell-local IDs as the primary identifier. + Rather use global IDs. +- Do not use cluster-wide database tables to store [static data](#static-data). +- Should only have a tiny amount of rows. Larger tables with many rows are not suitable to be cluster-wide tables. +- Must not have references to / from other tables that will cause data issues when synchronized to other cells. -Setting multiple `sharding_key`, with nullable columns are also allowed, provided that -the table has a check constraint that correctly ensures at least one of the keys must be non-nullable for a row in the table. -See [`NOT NULL` constraints for multiple columns](../database/not_null_constraints.md#not-null-constraints-for-multiple-columns) -for instructions on creating these constraints. - -The following are examples of valid sharding keys: - -- The table entries belong to a project only: - - ```yaml - sharding_key: - project_id: projects - ``` - -- The table entries belong to a project and the foreign key is `target_project_id`: - - ```yaml - sharding_key: - target_project_id: projects - ``` - -- The table entries belong to a namespace/group only: - - ```yaml - sharding_key: - namespace_id: namespaces - ``` - -- The table entries belong to a namespace/group only and the foreign key is `group_id`: - - ```yaml - sharding_key: - group_id: namespaces - ``` - -- The table entries belong to a namespace or a project: - - ```yaml - sharding_key: - project_id: projects - namespace_id: namespaces - ``` - -- (Only for `gitlab_main_user`) The table entries belong to a user only: - - ```yaml - sharding_key: - user_id: user - ``` - -### The sharding key must be immutable - -The choice of a `sharding_key` should always be immutable. This is because the -sharding key column will be used as an index for the planned -[Org Mover](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/migration/), -and also the -[enforcement of isolation](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/isolation/) -of Organization data. -Any mutation of the `sharding_key` could result in in-consistent data being read. - -Therefore, if your feature requires a user experience which allows data to be -moved between projects or groups/namespaces, then you may need to redesign the -move feature to create new rows. -An example of this can be seen in the -[move an issue feature](../../user/project/issues/managing_issues.md#move-an-issue). -This feature does not actually change the `project_id` column for an existing -`issues` row but instead creates a new `issues` row and creates a link in the -database from the original `issues` row. -If there is a particularly challenging -existing feature that needs to allow moving data you will need to reach out to -the Tenant Scale team early on to discuss options for how to manage the -sharding key. - -### Using `namespace_id` as sharding key - -The `namespaces` table has rows that can refer to a `Group`, a `ProjectNamespace`, -or a `UserNamespace`. The `UserNamespace` type is also known as a personal namespace. - -Using a `namespace_id` as a sharding key is a good option, except when `namespace_id` -refers to a `UserNamespace`. Because a user does not necessarily have a related -`namespace` record, this sharding key can be `NULL`. A sharding key should not -have `NULL` values. - -### Using the same sharding key for projects and namespaces - -Developers may also choose to use `namespace_id` only for tables that can -belong to a project where the feature used by the table is being developed -following the -[Consolidating Groups and Projects blueprint](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/consolidating_groups_and_projects/). -In that case the `namespace_id` would need to be the ID of the -`ProjectNamespace` and not the group that the namespace belongs to. - -### Using `organization_id` as sharding key - -Usually, `project_id` or `namespace_id` are the most common sharding keys. -However, there are cases where a table does not belong to a project or a namespace. - -In such cases, `organization_id` is an option for the sharding key, provided the below guidelines are followed: - -- The `sharding_key` column still needs to be [immutable](#the-sharding-key-must-be-immutable). -- Only add `organization_id` for root level models (for example, `namespaces`), and not leaf-level models (for example, `issues`). -- Ensure such tables do not contain data related to groups, or projects (or records that belong to groups / projects). - Instead, use `project_id`, or `namespace_id`. -- Tables with lots of rows are not good candidates because we would need to re-write every row if we move the entity to a different organization which can be expensive. -- When there are other tables referencing this table, the application should continue to work if the referencing table records are moved to a different organization. - -If you believe that the `organization_id` is the best option for the sharding key, seek approval from the Tenant Scale group. -This is crucial because it has implications for data migration and may require reconsideration of the choice of sharding key. - -As an example, see [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/462758), which added `organization_id` as a sharding key to an existing table. - -For more information about development with organizations, see [Organization](../organization) - -### Define a `desired_sharding_key` to automatically backfill a `sharding_key` - -We need to backfill a `sharding_key` to hundreds of tables that do not have one. -This process will involve creating a merge request like - to add the new -column, backfill the data from a related table in the database, and then create -subsequent merge requests to add indexes, foreign keys and not-null -constraints. - -In order to minimize the amount of repetitive effort for developers we've -introduced a concise declarative way to describe how to backfill the -`sharding_key` for this specific table. This content will later be used in -automation to create all the necessary merge requests. - -An example of the `desired_sharding_key` was added in - and it looks like: - -```yaml ---- # db/docs/security_findings.yml -table_name: security_findings -classes: -- Security::Finding - -# ... - -desired_sharding_key: - project_id: - references: projects - backfill_via: - parent: - foreign_key: scanner_id - table: vulnerability_scanners - table_primary_key: id # Optional. Defaults to 'id' - sharding_key: project_id - belongs_to: scanner -``` - -To understand best how this YAML data will be used you can map it onto -the merge request we created manually in GraphQL -. The idea -will be to automatically create this. The content of the YAML specifies -the parent table and its `sharding_key` to backfill from in the batched -background migration. It also specifies a `belongs_to` relation which -will be added to the model to automatically populate the `sharding_key` in -the `before_save`. - -#### Define a `desired_sharding_key` when the parent table also has one - -By default, a `desired_sharding_key` configuration will validate that the chosen `sharding_key` -exists on the parent table. However, if the parent table also has a `desired_sharding_key` configuration -and is itself waiting to be backfilled, you need to include the `awaiting_backfill_on_parent` field. -For example: - -```yaml -desired_sharding_key: - project_id: - references: projects - backfill_via: - parent: - foreign_key: package_file_id - table: packages_package_files - table_primary_key: id # Optional. Defaults to 'id' - sharding_key: project_id - belongs_to: package_file - awaiting_backfill_on_parent: true -``` - -There are likely edge cases where this `desired_sharding_key` structure is not -suitable for backfilling a `sharding_key`. In such cases the team owning the -table will need to create the necessary merge requests to add the -`sharding_key` manually. - -### Exempting certain tables from having sharding keys - -Certain tables can be exempted from having sharding keys by adding - -```yaml -exempt_from_sharding: true -``` - -to the table's database dictionary file. This can be used for: - -- JiHu specific tables, since they do not have any data on the .com database. [!145905](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/145905) -- tables that are marked to be dropped soon, like `operations_feature_flag_scopes`. [!147541](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147541) - -When tables are exempted from sharding key requirements, they also do not show up in our -[progress dashboard](https://cells-progress-tracker-gitlab-org-tenant-scale-g-f4ad96bf01d25f.gitlab.io/sharding_keys). - -Exempted tables must not have foreign key, or loose foreign key references, as -this may cause the target cell's database to have foreign key violations when data is -moved. -See [#471182](https://gitlab.com/gitlab-org/gitlab/-/issues/471182) for examples and possible solutions. - -## Ensure sharding key presence on application level - -When you define your sharding key you must make sure it's filled on application level. -Every `ApplicationRecord` model includes a helper `populate_sharding_key`, which -provides a convenient way of defining sharding key logic, -and also a corresponding matcher to test your sharding key logic. For example: - -```ruby -# in model.rb -populate_sharding_key :project_id, source: :merge_request, field: :target_project_id - -# in model_spec.rb -it { is_expected.to populate_sharding_key(:project_id).from(:merge_request, :target_project_id) } -``` - -See more [helper examples](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/populates_sharding_key.rb) -and [RSpec matcher examples](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/support/matchers/populate_sharding_key_matcher.rb). +We may ask teams to update tables from `gitlab_main_clusterwide` to `gitlab_main_cell` as required, which also might require adding sharding keys to these tables. ## Static data @@ -376,3 +141,7 @@ Examples of hard-coding static data include: - [VisibilityLevel](https://gitlab.com/gitlab-org/gitlab/-/blob/5ae43dface737373c50798ccd909174bcdd9b664/lib/gitlab/visibility_level.rb#L25-27) - [Static defaults for work item statuses](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/178180) + +## Cells Routing + +Coming soon, guide on how to route your request to your organization's cell. diff --git a/doc/development/database/multiple_databases.md b/doc/development/database/multiple_databases.md index 0299d9c1b35..f916fc639e8 100644 --- a/doc/development/database/multiple_databases.md +++ b/doc/development/database/multiple_databases.md @@ -51,15 +51,10 @@ The usage of schema enforces the base class to be used: - `PackageMetadata::ApplicationRecord` for `gitlab_pm` - `SecApplicationRecord` for `gitlab_sec` -### Choose either the `gitlab_main_cell` or `gitlab_main_clusterwide` schema - -This content has been moved to a -[new location](../cells/_index.md#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema) - ### Defining a sharding key for all cell-local tables This content has been moved to a -[new location](../cells/_index.md#defining-a-sharding-key-for-all-organizational-tables) +[new location](../organization/_index.md#defining-a-sharding-key-for-all-organizational-tables) ### The impact of `gitlab_schema` diff --git a/doc/development/organization/_index.md b/doc/development/organization/_index.md index 6da89050e88..69e93a057d8 100644 --- a/doc/development/organization/_index.md +++ b/doc/development/organization/_index.md @@ -80,6 +80,253 @@ When working on settings, we need to make sure that: For the [Cells](../cells) project, GitLab will rely on organizations. A cell will host one or more organizations. When a request is made, the [HTTP Router Service](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/http_routing_service/) will route it to the correct cell. +### Defining a sharding key for all organizational tables + +All tables with the following [`gitlab_schema`](../cells/_index.md#available-cells--organization-schemas) are considered organization level: + +- `gitlab_main_cell` +- `gitlab_ci` +- `gitlab_sec` +- `gitlab_main_user` + +All newly created organization-level tables are required to have a `sharding_key` +defined in the corresponding `db/docs/` file for that table. + +The purpose of the sharding key is documented in the +[Organization isolation blueprint](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/isolation/), +but in short this column is used to provide a standard way of determining which +Organization owns a particular row in the database. The column will be used in +the future to enforce constraints on data not cross Organization boundaries. It +will also be used in the future to provide a uniform way to migrate data +between Cells. + +The actual name of the foreign key can be anything but it must reference a row +in `projects` or `groups`. The chosen `sharding_key` column must be non-nullable. + +Setting multiple `sharding_key`, with nullable columns are also allowed, provided that +the table has a check constraint that correctly ensures at least one of the keys must be non-nullable for a row in the table. +See [`NOT NULL` constraints for multiple columns](../database/not_null_constraints.md#not-null-constraints-for-multiple-columns) +for instructions on creating these constraints. + +The following are examples of valid sharding keys: + +- The table entries belong to a project only: + + ```yaml + sharding_key: + project_id: projects + ``` + +- The table entries belong to a project and the foreign key is `target_project_id`: + + ```yaml + sharding_key: + target_project_id: projects + ``` + +- The table entries belong to a namespace/group only: + + ```yaml + sharding_key: + namespace_id: namespaces + ``` + +- The table entries belong to a namespace/group only and the foreign key is `group_id`: + + ```yaml + sharding_key: + group_id: namespaces + ``` + +- The table entries belong to a namespace or a project: + + ```yaml + sharding_key: + project_id: projects + namespace_id: namespaces + ``` + +- (Only for `gitlab_main_user`) The table entries belong to a user only: + + ```yaml + sharding_key: + user_id: user + ``` + +#### The sharding key must be immutable + +The choice of a `sharding_key` should always be immutable. This is because the +sharding key column will be used as an index for the planned +[Org Mover](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/cells/migration/), +and also the +[enforcement of isolation](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/isolation/) +of Organization data. +Any mutation of the `sharding_key` could result in in-consistent data being read. + +Therefore, if your feature requires a user experience which allows data to be +moved between projects or groups/namespaces, then you may need to redesign the +move feature to create new rows. +An example of this can be seen in the +[move an issue feature](../../user/project/issues/managing_issues.md#move-an-issue). +This feature does not actually change the `project_id` column for an existing +`issues` row but instead creates a new `issues` row and creates a link in the +database from the original `issues` row. +If there is a particularly challenging +existing feature that needs to allow moving data you will need to reach out to +the Tenant Scale team early on to discuss options for how to manage the +sharding key. + +#### Using `namespace_id` as sharding key + +The `namespaces` table has rows that can refer to a `Group`, a `ProjectNamespace`, +or a `UserNamespace`. The `UserNamespace` type is also known as a personal namespace. + +Using a `namespace_id` as a sharding key is a good option, except when `namespace_id` +refers to a `UserNamespace`. Because a user does not necessarily have a related +`namespace` record, this sharding key can be `NULL`. A sharding key should not +have `NULL` values. + +#### Using the same sharding key for projects and namespaces + +Developers may also choose to use `namespace_id` only for tables that can +belong to a project where the feature used by the table is being developed +following the +[Consolidating Groups and Projects blueprint](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/consolidating_groups_and_projects/). +In that case the `namespace_id` would need to be the ID of the +`ProjectNamespace` and not the group that the namespace belongs to. + +#### Using `organization_id` as sharding key + +Usually, `project_id` or `namespace_id` are the most common sharding keys. +However, there are cases where a table does not belong to a project or a namespace. + +In such cases, `organization_id` is an option for the sharding key, provided the below guidelines are followed: + +- The `sharding_key` column still needs to be [immutable](#the-sharding-key-must-be-immutable). +- Only add `organization_id` for root level models (for example, `namespaces`), and not leaf-level models (for example, `issues`). +- Ensure such tables do not contain data related to groups, or projects (or records that belong to groups / projects). + Instead, use `project_id`, or `namespace_id`. +- Tables with lots of rows are not good candidates because we would need to re-write every row if we move the entity to a different organization which can be expensive. +- When there are other tables referencing this table, the application should continue to work if the referencing table records are moved to a different organization. + +If you believe that the `organization_id` is the best option for the sharding key, seek approval from the Tenant Scale group. +This is crucial because it has implications for data migration and may require reconsideration of the choice of sharding key. + +As an example, see [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/462758), which added `organization_id` as a sharding key to an existing table. + +For more information about development with organizations, see [Organization](../organization) + +#### Define a `desired_sharding_key` to automatically backfill a `sharding_key` + +We need to backfill a `sharding_key` to hundreds of tables that do not have one. +This process will involve creating a merge request like + to add the new +column, backfill the data from a related table in the database, and then create +subsequent merge requests to add indexes, foreign keys and not-null +constraints. + +In order to minimize the amount of repetitive effort for developers we've +introduced a concise declarative way to describe how to backfill the +`sharding_key` for this specific table. This content will later be used in +automation to create all the necessary merge requests. + +An example of the `desired_sharding_key` was added in + and it looks like: + +```yaml +--- # db/docs/security_findings.yml +table_name: security_findings +classes: +- Security::Finding + +# ... + +desired_sharding_key: + project_id: + references: projects + backfill_via: + parent: + foreign_key: scanner_id + table: vulnerability_scanners + table_primary_key: id # Optional. Defaults to 'id' + sharding_key: project_id + belongs_to: scanner +``` + +To understand best how this YAML data will be used you can map it onto +the merge request we created manually in GraphQL +. The idea +will be to automatically create this. The content of the YAML specifies +the parent table and its `sharding_key` to backfill from in the batched +background migration. It also specifies a `belongs_to` relation which +will be added to the model to automatically populate the `sharding_key` in +the `before_save`. + +##### Define a `desired_sharding_key` when the parent table also has one + +By default, a `desired_sharding_key` configuration will validate that the chosen `sharding_key` +exists on the parent table. However, if the parent table also has a `desired_sharding_key` configuration +and is itself waiting to be backfilled, you need to include the `awaiting_backfill_on_parent` field. +For example: + +```yaml +desired_sharding_key: + project_id: + references: projects + backfill_via: + parent: + foreign_key: package_file_id + table: packages_package_files + table_primary_key: id # Optional. Defaults to 'id' + sharding_key: project_id + belongs_to: package_file + awaiting_backfill_on_parent: true +``` + +There are likely edge cases where this `desired_sharding_key` structure is not +suitable for backfilling a `sharding_key`. In such cases the team owning the +table will need to create the necessary merge requests to add the +`sharding_key` manually. + +#### Exempting certain tables from having sharding keys + +Certain tables can be exempted from having sharding keys by adding + +```yaml +exempt_from_sharding: true +``` + +to the table's database dictionary file. This can be used for: + +- JiHu specific tables, since they do not have any data on the .com database. [!145905](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/145905) +- tables that are marked to be dropped soon, like `operations_feature_flag_scopes`. [!147541](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147541) + +When tables are exempted from sharding key requirements, they also do not show up in our +[progress dashboard](https://cells-progress-tracker-gitlab-org-tenant-scale-g-f4ad96bf01d25f.gitlab.io/sharding_keys). + +Exempted tables must not have foreign key, or loose foreign key references, as +this may cause the target cell's database to have foreign key violations when data is +moved. +See [#471182](https://gitlab.com/gitlab-org/gitlab/-/issues/471182) for examples and possible solutions. + +### Ensure sharding key presence on application level + +When you define your sharding key you must make sure it's filled on application level. +Every `ApplicationRecord` model includes a helper `populate_sharding_key`, which +provides a convenient way of defining sharding key logic, +and also a corresponding matcher to test your sharding key logic. For example: + +```ruby +# in model.rb +populate_sharding_key :project_id, source: :merge_request, field: :target_project_id + +# in model_spec.rb +it { is_expected.to populate_sharding_key(:project_id).from(:merge_request, :target_project_id) } +``` + +See more [helper examples](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/populates_sharding_key.rb) +and [RSpec matcher examples](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/support/matchers/populate_sharding_key_matcher.rb). + ### Map a request to an organization with `Current.organization` The application needs to know how to map incoming requests to an organization. The mapping logic is encapsulated in [`Gitlab::Current::Organization`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/current/organization.rb). The outcome of this mapping is stored in a [`ActiveSupport::CurrentAttributes`](https://api.rubyonrails.org/classes/ActiveSupport/CurrentAttributes.html) instance called `Current`. You can then access the current organization using the `Current.organization` method. diff --git a/spec/lib/gitlab/database/no_new_tables_with_gitlab_main_schema_spec.rb b/spec/lib/gitlab/database/no_new_tables_with_gitlab_main_schema_spec.rb index 41ab614b0fc..aef8b786367 100644 --- a/spec/lib/gitlab/database/no_new_tables_with_gitlab_main_schema_spec.rb +++ b/spec/lib/gitlab/database/no_new_tables_with_gitlab_main_schema_spec.rb @@ -38,12 +38,10 @@ RSpec.describe 'new tables with gitlab_main schema', feature_category: :cell do <<~HEREDOC The table `#{table_name}` has been added with `gitlab_main` schema. Starting from GitLab #{starting_from_milestone}, we expect new tables to use either the `gitlab_main_cell` or the - `gitlab_main_clusterwide` schema. + `gitlab_main_cell_local`, or `gitlab_main_user` schema. - To choose an appropriate schema for this table from among `gitlab_main_cell` and `gitlab_main_clusterwide`, please refer - to our guidelines at https://docs.gitlab.com/ee/development/cells/#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema, or consult with the Tenant Scale group. - - Please see issue https://gitlab.com/gitlab-org/gitlab/-/issues/424990 to understand why this change is being enforced. + To choose an appropriate schema for this table, please refer + to our guidelines at https://docs.gitlab.com/ee/development/cells/#available-cells--organization-schemas or consult with the Tenant Scale group. HEREDOC end diff --git a/spec/lib/gitlab/database/sharding_key_spec.rb b/spec/lib/gitlab/database/sharding_key_spec.rb index f5cfbaf7757..8e2439a9c5d 100644 --- a/spec/lib/gitlab/database/sharding_key_spec.rb +++ b/spec/lib/gitlab/database/sharding_key_spec.rb @@ -160,7 +160,7 @@ RSpec.describe 'new tables missing sharding_key', feature_category: :organizatio expect(allowed_to_be_missing_sharding_key).to include(table_name), "This table #{table_name} is missing `sharding_key` in the `db/docs` YML file. " \ "Alternatively, set either a `sharding_key_issue_url`, or desired_sharding_key` attribute. " \ - "Please refer to https://docs.gitlab.com/development/cells/#defining-a-sharding-key-for-all-organizational-tables." + "Please refer to https://docs.gitlab.com/development/organization/#defining-a-sharding-key-for-all-organizational-tables." end end @@ -453,7 +453,7 @@ RSpec.describe 'new tables missing sharding_key', feature_category: :organizatio Starting from GitLab #{starting_from_milestone}, we expect all new tables to define a `sharding_key`. To choose an appropriate sharding_key for this table please refer - to our guidelines at https://docs.gitlab.com/ee/development/cells/#defining-a-sharding-key-for-all-cell-local-tables, or consult with the Tenant Scale group. + to our guidelines at https://docs.gitlab.com/ee/development/organization/#defining-a-sharding-key-for-all-cell-local-tables, or consult with the Tenant Scale group. HEREDOC end diff --git a/tooling/danger/gitlab_schema_validation_suggestion.rb b/tooling/danger/gitlab_schema_validation_suggestion.rb index 2c6234d854e..a5d4ba2d250 100644 --- a/tooling/danger/gitlab_schema_validation_suggestion.rb +++ b/tooling/danger/gitlab_schema_validation_suggestion.rb @@ -12,12 +12,12 @@ module Tooling DB_DOCS_PATH = %r{\Adb/docs/[^/]+\.ya?ml\z} SUGGESTION = <<~MESSAGE_MARKDOWN - :warning: You have added `gitlab_main_clusterwide` as the schema for this table. We expect most tables to use the - `gitlab_main_cell` schema instead, as using the clusterwide schema can have significant scaling implications. + :warning: You have added `gitlab_main_clusterwide` (deprecated) as the schema for this table. We expect most tables to use the + `gitlab_main_cell` schema instead. - Please see the [guidelines on choosing gitlab schema](https://docs.gitlab.com/ee/development/cells/#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema) for more information. + Please see the [guidelines on choosing gitlab schema](https://docs.gitlab.com/ee/development/cells/#what-schema-to-choose-if-the-feature-can-be-cluster-wide) for more information. - Please consult with `@gitlab-com/gl-infra/tenant-scale/organizations` if you believe that the clusterwide schema is the best fit for this table. + Please consult with `@gitlab-com/gl-infra/tenant-scale/cells-infrastructure` if you believe that the clusterwide schema is the best fit for this table. MESSAGE_MARKDOWN def add_suggestions_on_using_clusterwide_schema