diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-31 03:16:38 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-31 03:16:38 +0300 |
commit | 453bb35fc81741c1dd7178cde1f64df2c9ec7252 (patch) | |
tree | 44edb488772b5fc89967865e4e0e70c8feab832f /doc/user | |
parent | 892e58c41fd07cc59b9e06b2a856ee61790d5bc4 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/group/manage.md | 5 | ||||
-rw-r--r-- | doc/user/packages/maven_repository/index.md | 2 | ||||
-rw-r--r-- | doc/user/project/members/share_project_with_groups.md | 5 | ||||
-rw-r--r-- | doc/user/project/merge_requests/index.md | 28 |
4 files changed, 39 insertions, 1 deletions
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md index d671b0434b6..d67e52a6fc3 100644 --- a/doc/user/group/manage.md +++ b/doc/user/group/manage.md @@ -130,6 +130,11 @@ After sharing the `Frontend` group with the `Engineering` group: - The **Groups** tab lists the `Engineering` group. - The **Groups** tab lists a group regardless of whether it is a public or private group. +- From [GitLab 16.6](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134623), + the invited group's name and membership source will be hidden unless: + - the invited group is public, or + - the current user is a member of the invited group, or + - the current user is a member of the current group. - All direct members of the `Engineering` group have access to the `Frontend` group. The least access is granted between the access in the `Engineering` group and the access in the `Frontend` group. - If `Member1` has the Maintainer role in `Engineering` and `Engineering` is added to `Frontend` with the Developer role, `Member1` has the Developer role in `Frontend`. - If `Member2` has the Guest role in `Engineering` and `Engineering` is added to `Frontend` with the Developer role, `Member2` has the Guest role in `Frontend`. diff --git a/doc/user/packages/maven_repository/index.md b/doc/user/packages/maven_repository/index.md index 6765aa2cbb1..2c395538455 100644 --- a/doc/user/packages/maven_repository/index.md +++ b/doc/user/packages/maven_repository/index.md @@ -24,7 +24,7 @@ Supported clients: ### Authenticate to the Package Registry -You need an token to publish a package. There are different tokens available depending on what you're trying to achieve. For more information, review the [guidance on tokens](../package_registry/index.md#authenticate-with-the-registry). +You need a token to publish a package. There are different tokens available depending on what you're trying to achieve. For more information, review the [guidance on tokens](../package_registry/index.md#authenticate-with-the-registry). Create a token and save it to use later in the process. diff --git a/doc/user/project/members/share_project_with_groups.md b/doc/user/project/members/share_project_with_groups.md index deefe9040fa..4474cb55929 100644 --- a/doc/user/project/members/share_project_with_groups.md +++ b/doc/user/project/members/share_project_with_groups.md @@ -76,6 +76,11 @@ In addition: - On the group's page, the project is listed on the **Shared projects** tab. - On the project's **Members** page, the group is listed on the **Groups** tab. +- From [GitLab 16.6](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134623), + the invited group's name and membership source will be hidden unless: + - the group is public, or + - the current user is a member of the group, or + - the current user is a member of the project. - Each user is assigned a maximum role. - Members who have the **Project Invite** badge next to their profile on the usage quota page count towards the billable members of the shared project's top-level group. diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md index 22cd8f9b89e..58cfd90c13f 100644 --- a/doc/user/project/merge_requests/index.md +++ b/doc/user/project/merge_requests/index.md @@ -489,3 +489,31 @@ p = Project.find_by_full_path('<namespace/project>') m = p.merge_requests.find_by(iid: <iid>) Issuable::DestroyService.new(container: m.project, current_user: u).execute(m) ``` + +### Merge request pre-receive hook failed + +If a merge request times out, you might see messages that indicate a Puma worker +timeout problem: + +- In the GitLab UI: + + ```plaintext + Something went wrong during merge pre-receive hook. + 500 Internal Server Error. Try again. + ``` + +- In the `gitlab-rails/api_json.log` log file: + + ```plaintext + Rack::Timeout::RequestTimeoutException + Request ran for longer than 60000ms + ``` + +This error can happen if your merge request: + +- Contains many diffs. +- Is many commits behind the target branch. + +Users in self-managed installations can request an administrator review server logs +to determine the cause of the error. GitLab SaaS users should +[contact Support](https://about.gitlab.com/support/#contact-support) for help. |