Skip to content
Snippets Groups Projects
Commit a3f7526b authored by 🤖 GitLab Bot 🤖's avatar 🤖 GitLab Bot 🤖
Browse files

Add latest changes from gitlab-org/gitlab@master

parent 50599a24
No related branches found
No related tags found
No related merge requests found
Pipeline #1671930541 passed
Stage: sync
Stage: preflight
Stage: prepare
Stage: build-images
Stage: fixtures
Stage: lint
Stage: test-frontend
Stage: test
Stage: post-test
Stage: pages
Stage: benchmark
Hide whitespace changes
Inline Side-by-side
Showing
with 43 additions and 141 deletions
.rubocop_todo/gitlab/bounded_contexts.yml
+ 0
− 4
View file @ a3f7526b
......@@ -2249,7 +2249,6 @@ Gitlab/BoundedContexts:
- 'ee/app/graphql/mutations/epics/create.rb'
- 'ee/app/graphql/mutations/epics/set_subscription.rb'
- 'ee/app/graphql/mutations/epics/update.rb'
- 'ee/app/graphql/mutations/forecasting/build_forecast.rb'
- 'ee/app/graphql/mutations/groups/saved_replies/create.rb'
- 'ee/app/graphql/mutations/groups/saved_replies/destroy.rb'
- 'ee/app/graphql/mutations/groups/saved_replies/update.rb'
......@@ -2435,9 +2434,6 @@ Gitlab/BoundedContexts:
- 'ee/app/graphql/types/epics/unioned_epic_filter_input_type.rb'
- 'ee/app/graphql/types/external_issue_type.rb'
- 'ee/app/graphql/types/feature_flag_type.rb'
- 'ee/app/graphql/types/forecasting/datapoint_type.rb'
- 'ee/app/graphql/types/forecasting/forecast_status_enum.rb'
- 'ee/app/graphql/types/forecasting/forecast_type.rb'
- 'ee/app/graphql/types/google_cloud/artifact_registry/artifact_details_type.rb'
- 'ee/app/graphql/types/google_cloud/artifact_registry/artifact_type.rb'
- 'ee/app/graphql/types/google_cloud/artifact_registry/artifacts_sort_enum.rb'
......
.rubocop_todo/gitlab/documentation_links/link.yml
+ 0
− 1
View file @ a3f7526b
......@@ -13,5 +13,4 @@ Gitlab/DocumentationLinks/Link:
- 'ee/spec/support/shared_contexts/secrets_check_shared_contexts.rb'
- 'lib/backup/tasks/database.rb'
- 'lib/system_check/helpers.rb'
- 'spec/mailers/emails/pages_domains_spec.rb'
- 'spec/presenters/commit_status_presenter_spec.rb'
.rubocop_todo/rails/date.yml
+ 0
− 5
View file @ a3f7526b
......@@ -21,7 +21,6 @@ Rails/Date:
- 'ee/app/controllers/groups/analytics/tasks_by_type_controller.rb'
- 'ee/app/finders/iterations_finder.rb'
- 'ee/app/finders/okrs/checkin_reminder_key_result_finder.rb'
- 'ee/app/models/analytics/forecasting/forecast.rb'
- 'ee/app/models/burndown.rb'
- 'ee/app/models/ee/epic.rb'
- 'ee/app/models/ee/namespace.rb'
......@@ -60,7 +59,6 @@ Rails/Date:
- 'ee/spec/features/projects/milestones/milestone_spec.rb'
- 'ee/spec/features/promotion_spec.rb'
- 'ee/spec/finders/iterations_finder_spec.rb'
- 'ee/spec/graphql/mutations/forecasting/build_forecast_spec.rb'
- 'ee/spec/helpers/timeboxes_helper_spec.rb'
- 'ee/spec/lib/analytics/dora_performance_score_calculator_spec.rb'
- 'ee/spec/lib/analytics/productivity_analytics_request_params_spec.rb'
......@@ -73,8 +71,6 @@ Rails/Date:
- 'ee/spec/lib/gitlab/contribution_analytics/postgresql_data_collector_spec.rb'
- 'ee/spec/lib/gitlab/insights/loader_spec.rb'
- 'ee/spec/lib/gitlab/sitemaps/sitemap_file_spec.rb'
- 'ee/spec/models/analytics/forecasting/deployment_frequency_forecast_spec.rb'
- 'ee/spec/models/analytics/forecasting/forecast_spec.rb'
- 'ee/spec/models/burndown_spec.rb'
- 'ee/spec/models/ci/minutes/namespace_monthly_usage_spec.rb'
- 'ee/spec/models/dora/performance_score_spec.rb'
......@@ -84,7 +80,6 @@ Rails/Date:
- 'ee/spec/models/gitlab_subscription_spec.rb'
- 'ee/spec/models/iteration_spec.rb'
- 'ee/spec/models/search/zoekt/enabled_namespace_spec.rb'
- 'ee/spec/requests/api/graphql/mutations/forecasting/build_forecast_spec.rb'
- 'ee/spec/requests/api/group_milestones_spec.rb'
- 'ee/spec/requests/api/group_service_accounts_spec.rb'
- 'ee/spec/requests/api/issues_spec.rb'
......
.rubocop_todo/rspec/be_eq.yml
+ 0
− 2
View file @ a3f7526b
......@@ -193,7 +193,6 @@ RSpec/BeEq:
- 'ee/spec/lib/users/identity_verification/authorize_ci_spec.rb'
- 'ee/spec/models/alert_management/alert_payload_field_spec.rb'
- 'ee/spec/models/allowed_email_domain_spec.rb'
- 'ee/spec/models/analytics/forecasting/forecast_spec.rb'
- 'ee/spec/models/analytics/value_stream_dashboard/count_spec.rb'
- 'ee/spec/models/approval_merge_request_rule_spec.rb'
- 'ee/spec/models/approval_project_rule_spec.rb'
......@@ -394,7 +393,6 @@ RSpec/BeEq:
- 'ee/spec/serializers/member_user_entity_spec.rb'
- 'ee/spec/serializers/merge_request_widget_entity_spec.rb'
- 'ee/spec/services/analytics/cycle_analytics/value_streams/create_service_spec.rb'
- 'ee/spec/services/analytics/forecasting/build_forecast_service_spec.rb'
- 'ee/spec/services/approval_rules/create_service_spec.rb'
- 'ee/spec/services/approval_rules/finalize_service_spec.rb'
- 'ee/spec/services/boards/user_preferences/update_service_spec.rb'
......
.rubocop_todo/rspec/named_subject.yml
+ 0
− 6
View file @ a3f7526b
......@@ -121,7 +121,6 @@ RSpec/NamedSubject:
- 'ee/spec/graphql/mutations/epics/add_issue_spec.rb'
- 'ee/spec/graphql/mutations/epics/create_spec.rb'
- 'ee/spec/graphql/mutations/epics/update_spec.rb'
- 'ee/spec/graphql/mutations/forecasting/build_forecast_spec.rb'
- 'ee/spec/graphql/mutations/instance_security_dashboard/add_project_spec.rb'
- 'ee/spec/graphql/mutations/instance_security_dashboard/remove_project_spec.rb'
- 'ee/spec/graphql/mutations/issues/promote_to_epic_spec.rb'
......@@ -204,8 +203,6 @@ RSpec/NamedSubject:
- 'ee/spec/initializers/session_store_spec.rb'
- 'ee/spec/lib/analytics/devops_adoption/snapshot_calculator_spec.rb'
- 'ee/spec/lib/analytics/dora_metrics_aggregator_spec.rb'
- 'ee/spec/lib/analytics/forecasting/holt_winters_optimizer_spec.rb'
- 'ee/spec/lib/analytics/forecasting/holt_winters_spec.rb'
- 'ee/spec/lib/analytics/group_activity_calculator_spec.rb'
- 'ee/spec/lib/analytics/merge_request_metrics_calculator_spec.rb'
- 'ee/spec/lib/analytics/merge_request_metrics_refresh_spec.rb'
......@@ -465,8 +462,6 @@ RSpec/NamedSubject:
- 'ee/spec/mailers/notify_spec.rb'
- 'ee/spec/models/allowed_email_domain_spec.rb'
- 'ee/spec/models/analytics/cycle_analytics/group_level_spec.rb'
- 'ee/spec/models/analytics/forecasting/deployment_frequency_forecast_spec.rb'
- 'ee/spec/models/analytics/forecasting/forecast_spec.rb'
- 'ee/spec/models/approval_merge_request_rule_spec.rb'
- 'ee/spec/models/approval_project_rule_spec.rb'
- 'ee/spec/models/approval_state_spec.rb'
......@@ -789,7 +784,6 @@ RSpec/NamedSubject:
- 'ee/spec/services/analytics/devops_adoption/snapshots/calculate_and_save_service_spec.rb'
- 'ee/spec/services/analytics/devops_adoption/snapshots/create_service_spec.rb'
- 'ee/spec/services/analytics/devops_adoption/snapshots/update_service_spec.rb'
- 'ee/spec/services/analytics/forecasting/build_forecast_service_spec.rb'
- 'ee/spec/services/app_sec/dast/pipelines/find_latest_service_spec.rb'
- 'ee/spec/services/app_sec/dast/pre_scan_verification_steps/create_or_update_service_spec.rb'
- 'ee/spec/services/app_sec/dast/pre_scan_verification_steps/find_or_create_service_spec.rb'
......
.rubocop_todo/rspec/verified_double_reference.yml
+ 0
− 4
View file @ a3f7526b
......@@ -9,7 +9,6 @@ RSpec/VerifiedDoubleReference:
- 'ee/spec/features/merge_request/user_sees_security_policy_rules_licence_compliance_spec.rb'
- 'ee/spec/features/projects/google_cloud/artifact_registry_spec.rb'
- 'ee/spec/features/projects/integrations/google_cloud_platform/user_activates_artifact_management_spec.rb'
- 'ee/spec/graphql/mutations/forecasting/build_forecast_spec.rb'
- 'ee/spec/helpers/groups/sso_helper_spec.rb'
- 'ee/spec/helpers/vulnerabilities_helper_spec.rb'
- 'ee/spec/lib/ai/context/dependencies/config_files/base_spec.rb'
......@@ -34,8 +33,6 @@ RSpec/VerifiedDoubleReference:
- 'ee/spec/lib/security/security_orchestration_policies/policy_diff/rules_diff_spec.rb'
- 'ee/spec/migrations/geo/resync_direct_upload_job_artifact_registry_spec.rb'
- 'ee/spec/models/analytics/cycle_analytics/aggregation_context_spec.rb'
- 'ee/spec/models/analytics/forecasting/deployment_frequency_forecast_spec.rb'
- 'ee/spec/models/analytics/forecasting/forecast_spec.rb'
- 'ee/spec/models/concerns/projects/custom_branch_rule_spec.rb'
- 'ee/spec/models/container_repository_spec.rb'
- 'ee/spec/models/ee/user_spec.rb'
......@@ -56,7 +53,6 @@ RSpec/VerifiedDoubleReference:
- 'ee/spec/serializers/dashboard_environments_project_entity_spec.rb'
- 'ee/spec/serializers/vulnerabilities/finding_entity_spec.rb'
- 'ee/spec/services/analytics/cycle_analytics/consistency_check_service_spec.rb'
- 'ee/spec/services/analytics/forecasting/build_forecast_service_spec.rb'
- 'ee/spec/services/app_sec/dast/scans/run_service_spec.rb'
- 'ee/spec/services/ee/integrations/test/project_service_spec.rb'
- 'ee/spec/services/ee/merge_request_metrics_service_spec.rb'
......
.rubocop_todo/style/inline_disable_annotation.yml
+ 0
− 2
View file @ a3f7526b
......@@ -1102,8 +1102,6 @@ Style/InlineDisableAnnotation:
- 'ee/app/graphql/types/epic_health_status_type.rb'
- 'ee/app/graphql/types/epic_issue_type.rb'
- 'ee/app/graphql/types/external_issue_type.rb'
- 'ee/app/graphql/types/forecasting/datapoint_type.rb'
- 'ee/app/graphql/types/forecasting/forecast_type.rb'
- 'ee/app/graphql/types/geo/registry_class_enum.rb'
- 'ee/app/graphql/types/gitlab_subscriptions/preview_billable_user_change_type.rb'
- 'ee/app/graphql/types/incident_management/escalation_rule_input_type.rb'
......
GITLAB_KAS_VERSION
+ 1
− 1
View file @ a3f7526b
737917b4ec3db719fbed640d2c9cbd9be6e38b05
cc01f56459190de381f72938ed458d37e9708110
doc/api/graphql/reference/_index.md
+ 0
− 79
View file @ a3f7526b
......@@ -3145,31 +3145,6 @@ Input type: `BranchRuleUpdateInput`
| <a id="mutationbranchruleupdateclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
| <a id="mutationbranchruleupdateerrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
 
### `Mutation.buildForecast`
DETAILS:
**Introduced** in GitLab 16.0.
**Status**: Experiment.
Input type: `BuildForecastInput`
#### Arguments
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="mutationbuildforecastclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
| <a id="mutationbuildforecastcontextid"></a>`contextId` | [`GlobalID!`](#globalid) | Global ID of the context for the forecast to pick an appropriate model. |
| <a id="mutationbuildforecasthorizon"></a>`horizon` | [`Int!`](#int) | Number of data points to forecast. |
| <a id="mutationbuildforecasttype"></a>`type` | [`String!`](#string) | Type of the forecast. |
#### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="mutationbuildforecastclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
| <a id="mutationbuildforecasterrors"></a>`errors` | [`[String!]!`](#string) | Errors encountered during execution of the mutation. |
| <a id="mutationbuildforecastforecast"></a>`forecast` | [`Forecast!`](#forecast) | Created forecast. |
### `Mutation.bulkDestroyJobArtifacts`
 
DETAILS:
......@@ -15213,29 +15188,6 @@ The edge type for [`FeatureFlag`](#featureflag).
| <a id="featureflagedgecursor"></a>`cursor` | [`String!`](#string) | A cursor for use in pagination. |
| <a id="featureflagedgenode"></a>`node` | [`FeatureFlag`](#featureflag) | The item at the end of the edge. |
 
#### `ForecastDatapointConnection`
The connection type for [`ForecastDatapoint`](#forecastdatapoint).
##### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="forecastdatapointconnectionedges"></a>`edges` | [`[ForecastDatapointEdge]`](#forecastdatapointedge) | A list of edges. |
| <a id="forecastdatapointconnectionnodes"></a>`nodes` | [`[ForecastDatapoint]`](#forecastdatapoint) | A list of nodes. |
| <a id="forecastdatapointconnectionpageinfo"></a>`pageInfo` | [`PageInfo!`](#pageinfo) | Information to aid in pagination. |
#### `ForecastDatapointEdge`
The edge type for [`ForecastDatapoint`](#forecastdatapoint).
##### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="forecastdatapointedgecursor"></a>`cursor` | [`String!`](#string) | A cursor for use in pagination. |
| <a id="forecastdatapointedgenode"></a>`node` | [`ForecastDatapoint`](#forecastdatapoint) | The item at the end of the edge. |
#### `GitlabSubscriptionHistoryConnection`
 
The connection type for [`GitlabSubscriptionHistory`](#gitlabsubscriptionhistory).
......@@ -25296,28 +25248,6 @@ Represents security reports comparison for vulnerability findings.
| <a id="findingreportscomparerstatus"></a>`status` | [`FindingReportsComparerStatus`](#findingreportscomparerstatus) | Comparison status. |
| <a id="findingreportscomparerstatusreason"></a>`statusReason` | [`String`](#string) | Text explaining the status. |
 
### `Forecast`
Information about specific forecast created.
#### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="forecaststatus"></a>`status` | [`ForecastStatus!`](#forecaststatus) | Status of the forecast. |
| <a id="forecastvalues"></a>`values` | [`ForecastDatapointConnection`](#forecastdatapointconnection) | Actual forecast values. (see [Connections](#connections)) |
### `ForecastDatapoint`
Information about specific forecast datapoint.
#### Fields
| Name | Type | Description |
| ---- | ---- | ----------- |
| <a id="forecastdatapointdatapoint"></a>`datapoint` | [`String!`](#string) | Datapoint of the forecast. Usually a date. |
| <a id="forecastdatapointvalue"></a>`value` | [`Float`](#float) | Value of the given datapoint. |
### `ForkDetails`
 
Details of the fork project compared to its upstream project.
......@@ -41102,15 +41032,6 @@ Report comparison status.
| <a id="findingreportscomparerstatusparsed"></a>`PARSED` | Report was generated. |
| <a id="findingreportscomparerstatusparsing"></a>`PARSING` | Report is being generated. |
 
### `ForecastStatus`
List of statuses for forecasting model.
| Value | Description |
| ----- | ----------- |
| <a id="forecaststatusready"></a>`READY` | Forecast is ready. |
| <a id="forecaststatusunavailable"></a>`UNAVAILABLE` | Forecast is unavailable. |
### `GeoRegistriesBulkAction`
 
Action to trigger on multiple Geo registries.
doc/api/settings.md
+ 1
− 1
View file @ a3f7526b
......@@ -449,7 +449,7 @@ to configure other related settings. These requirements are
| `deactivate_dormant_users_period` | integer | no | Length of time (in days) after which a user is considered dormant. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/336747) in GitLab 15.3. |
| `decompress_archive_file_timeout` | integer | no | Default timeout for decompressing archived files, in seconds. Set to 0 to disable timeouts. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/129161) in GitLab 16.4. |
| `default_artifacts_expire_in` | string | no | Set the default expiration time for each job's artifacts. |
| `default_branch_name` | string | no | [Instance-level custom initial branch name](../user/project/repository/branches/default.md#instance-level-custom-initial-branch-name). |
| `default_branch_name` | string | no | [Set the initial branch name](../user/project/repository/branches/default.md#change-the-default-branch-name-for-new-projects-in-an-instance) for all projects in an instance. |
| `default_branch_protection` | integer | no | [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/408314) in GitLab 17.0. Use `default_branch_protection_defaults` instead. |
| `default_branch_protection_defaults` | hash | no | [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/408314) in GitLab 17.0. For available options, see [Options for `default_branch_protection_defaults`](groups.md#options-for-default_branch_protection_defaults). |
| `default_ci_config_path` | string | no | Default CI/CD configuration file and path for new projects (`.gitlab-ci.yml` if not set). |
......
doc/development/ai_features/glossary.md
+ 1
− 1
View file @ a3f7526b
......@@ -133,7 +133,7 @@ A mechanism used to take an input (such as a user question) into a system, retri
### Self-hosted model
A LLM hosted externally to GitLab by an organisation and interacting with GitLab AI features.
A LLM hosted externally to GitLab by an organisation and interacting with GitLab AI features. See also the [style guide reference](../../development/documentation/styleguide/word_list.md#self-hosted-model).
### Similarity Score
......
doc/development/internal_analytics/service_ping/_index.md
+ 4
− 4
View file @ a3f7526b
......@@ -39,7 +39,7 @@ We use the following terminology to describe the Service Ping components:
## Service Ping request flow
The following example shows a basic request/response flow between a GitLab instance, the Versions Application, the License Application, Salesforce, the GitLab S3 Bucket, the GitLab Snowflake Data Warehouse, and Tableau:
The following example shows a basic request/response flow between a GitLab instance, the Versions Application, the License Application, Salesforce, the GitLab GCP Bucket, the GitLab Snowflake Data Warehouse, and Tableau:
```mermaid
sequenceDiagram
......@@ -47,7 +47,7 @@ sequenceDiagram
participant Versions Application
participant Licenses Application
participant Salesforce
participant S3 Bucket
participant GCP Bucket
participant Snowflake DW
participant Tableau Dashboards
GitLab Instance->>Versions Application: Send Service Ping
......@@ -63,8 +63,8 @@ sequenceDiagram
Salesforce-xVersions Application: Zuora account id
Versions Application-xSalesforce: Usage data for the Zuora account
end
Versions Application->>S3 Bucket: Export Versions database
S3 Bucket->>Snowflake DW: Import data
Versions Application->>GCP Bucket: Export Versions database
GCP Bucket->>Snowflake DW: Import data
Snowflake DW->>Snowflake DW: Transform data using dbt
Snowflake DW->>Tableau Dashboards: Data available for querying
Versions Application->>GitLab Instance: DevOps Score (Conversational Development Index)
......
doc/tutorials/infrastructure.md
+ 2
− 3
View file @ a3f7526b
......@@ -11,6 +11,5 @@ configure the infrastructure for your application.
| Topic | Description | Good for beginners |
|-------|-------------|--------------------|
| [Use GitOps with GitLab](https://about.gitlab.com/blog/2022/04/07/the-ultimate-guide-to-gitops-with-gitlab/) | Learn how to provision and manage a base infrastructure, connect to a Kubernetes cluster, deploy third-party applications, and carry out other infrastructure automation tasks. | |
| [Get started connecting a Kubernetes cluster to GitLab](../user/clusters/agent/getting_started.md) | Learn how to set up the agent for Kubernetes with Flux for GitOps. | |
| [Get started deploying to Kubernetes](../user/clusters/agent/getting_started_deployments.md) | Learn how to deploy to a Kubernetes cluster with GitLab CI/CD. | |
| [Get started connecting a Kubernetes cluster to GitLab](../user/clusters/agent/getting_started.md) | Learn how to set up the agent for Kubernetes with Flux for GitOps. | **{star}** |
| [Get started deploying to Kubernetes](../user/clusters/agent/getting_started_deployments.md) | Learn how to deploy to a Kubernetes cluster with GitLab CI/CD. | **{star}** |
doc/user/gitlab_duo_chat/_index.md
+ 7
− 0
View file @ a3f7526b
......@@ -94,6 +94,13 @@ This applies to files added via `/include`, and all generation commands.
## Use GitLab Duo Chat in the GitLab UI
1. In the upper-right corner, select **GitLab Duo Chat**. A drawer opens on the right side of your screen.
> The **GitLab Duo Chat** button is **not visible** in the following sections:
>
> - Any of the **Your work** pages such as your [To-Do List](../todos.md).
> - Your [**user profile**](../profile/_index.md).
> - **Help**.
1. Enter your question in the chat input box and press **Enter** or select **Send**. It may take a few seconds for the interactive AI chat to produce an answer.
1. Optional. Ask a follow-up question.
......
doc/user/gitlab_duo_chat/examples.md
+ 3
− 0
View file @ a3f7526b
......@@ -10,6 +10,9 @@ represent some of the areas where GitLab Duo Chat can be the most helpful.
For additional practical examples, see the [GitLab Duo use cases](../gitlab_duo/use_cases.md).
NOTE:
The example questions on this page, including the [slash commands](#gitlab-duo-chat-slash-commands), are deliberately generic. You might receive more useful responses from Chat by asking questions that are specific to your current goal. For example, "How does the `clean_missing_data` function in `data_cleaning.py` decide which rows to drop?".
## Ask about GitLab
DETAILS:
......
doc/user/group/manage.md
+ 7
− 9
View file @ a3f7526b
......@@ -84,20 +84,18 @@ For more information about our solution to mitigate this timeout risk, see [issu
## Change the default branch protection of a group
By default, every group inherits the branch protection set at the global level.
To change this setting for a specific group, see [group level default branch protection](../project/repository/branches/default.md#group-level-default-branch-protection).
To change this setting globally, see [initial default branch protection](../project/repository/branches/default.md#instance-level-default-branch-protection).
NOTE:
In [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/), GitLab administrators can choose to [disable group Owners from updating the default branch protection](../project/repository/branches/default.md#prevent-overrides-of-default-branch-protection).
The administrator of a GitLab instance can configure default branch protections for
[all projects in an instance](../project/repository/branches/default.md#for-all-projects-in-an-instance).
Groups in that instance inherit the branch protection set at the global level. Group owners can
[override the instance settings](../project/repository/branches/default.md#for-all-projects-in-a-group)
for projects in a group. In [GitLab Premium or Ultimate](https://about.gitlab.com/pricing/), the administrator
of the instance can disable this privilege.
## Use a custom name for the initial branch
When you create a new project in GitLab, a default branch is created with the
first push. The group Owner can
[customize the initial branch](../project/repository/branches/default.md#group-level-custom-initial-branch-name)
[customize the initial branch](../project/repository/branches/default.md#change-the-default-branch-name-for-new-projects-in-a-group)
for the group's projects to meet your group's needs.
## Transfer a group
......
doc/user/group/saml_sso/troubleshooting_scim.md
+ 1
− 0
View file @ a3f7526b
......@@ -169,6 +169,7 @@ when the:
- User exists, but does not have a SAML identity linked.
- User exists, has a SAML identity, **and** has a SCIM identity that is set to `active: false`.
- User exists, but is not a member of the associated top-level group and SAML SSO enforcement is enabled.
```plaintext
The member's email address is not linked to a SAML account or has an inactive
......
doc/user/infrastructure/clusters/migrate_to_gitlab_agent.md
+ 1
− 0
View file @ a3f7526b
......@@ -80,6 +80,7 @@ Prerequisites:
To migrate from GitLab-managed clusters to GitLab-managed Kubernetes resources:
1. If you're migrating an existing environment, configure an agent for the environment either through the [dashboard for Kubernetes](../../../ci/environments/kubernetes_dashboard.md#configure-a-dashboard) or the [Environments API](../../../api/environments.md).
1. Configure the agent to turn on resource management in your agent configuration file:
```yaml
......
doc/user/project/repository/branches/default.md
+ 13
− 17
View file @ a3f7526b
......@@ -27,9 +27,9 @@ GitLab checks first for specific customizations, then checks at a broader level,
using the GitLab default only if no customizations are set:
1. A [project-specific](#change-the-default-branch-name-for-a-project) custom default branch name.
1. [Custom group default branch name](#group-level-custom-initial-branch-name) specified in project's direct subgroup.
1. [Custom group default branch name](#group-level-custom-initial-branch-name) specified in project's top-level group.
1. A custom default branch name set for the [instance](#instance-level-custom-initial-branch-name).
1. [Custom group default branch name](#change-the-default-branch-name-for-new-projects-in-a-group) specified in a project's direct subgroup.
1. Custom group default branch name specified in a project's top-level group.
1. A custom default branch name set for the [instance](#change-the-default-branch-name-for-new-projects-in-an-instance).
1. If no custom default branch name is set at any level, GitLab defaults to `main`.
In the GitLab UI, you can change the defaults at any level. GitLab also provides
......@@ -54,13 +54,7 @@ To update the default branch for an individual [project](../../_index.md):
API users can also use the `default_branch` attribute of the
[Projects API](../../../../api/projects.md) when creating or editing a project.
## Change the default branch name for an instance or group
GitLab administrators can configure a new default branch name for the
[entire instance](#instance-level-custom-initial-branch-name) or for
[individual groups](#group-level-custom-initial-branch-name).
### Instance-level custom initial branch name
## Change the default branch name for new projects in an instance
DETAILS:
**Tier:** Free, Premium, Ultimate
......@@ -80,9 +74,13 @@ Projects created on this instance after you change the setting use the
custom branch name, unless a group or subgroup configuration
overrides it.
### Group-level custom initial branch name
## Change the default branch name for new projects in a group
Prerequisites:
- You must have the Owner role for the group and subgroups.
Users with the Owner role of groups and subgroups can configure the default branch name for a group:
To change the default branch name for new projects in a group:
1. On the left sidebar, select **Search or go to** and find your group.
1. Select **Settings > Repository**.
......@@ -102,9 +100,7 @@ DETAILS:
> - Full protection after initial push [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/118729) in GitLab 16.0.
GitLab administrators and group owners can define [branch protections](protected.md)
to apply to every repository's default branch
[for the instance](#instance-level-default-branch-protection) and
[individual groups](#group-level-default-branch-protection) with one of the following options:
to apply to every repository's default branch for the instance, or for individual groups, with one of these options:
- **Fully protected** - Default value. Developers cannot push new commits, but maintainers can.
No one can force push.
......@@ -120,7 +116,7 @@ to apply to every repository's default branch
WARNING:
Unless **Fully protected** is chosen, a malicious developer could attempt to steal your sensitive data. For example, a malicious `.gitlab-ci.yml` file could be committed to a protected branch and later, if a pipeline is run against that branch, result in exfiltration of group CI/CD variables.
### Instance-level default branch protection
### For all projects in an instance
DETAILS:
**Tier:** Free, Premium, Ultimate
......@@ -163,7 +159,7 @@ disable this privilege for group owners, enforcing the protection rule set for t
NOTE:
GitLab administrators can still update the default branch protection of a group.
### Group-level default branch protection
### For all projects in a group
DETAILS:
**Tier:** Premium, Ultimate
......
doc/user/project/repository/branches/protected.md
+ 2
− 2
View file @ a3f7526b
......@@ -83,8 +83,8 @@ that matches `v1.x` must set `Allowed to push and merge` to `No one`, like this:
### Set the default branch protection level
Administrators can set a default branch protection level in the
[**Admin** area](default.md#instance-level-default-branch-protection).
Administrators can [set a default branch protection level](default.md#for-all-projects-in-an-instance)
in the **Admin** area.
## Add protection to existing branches
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment