Commit 7e208091 authored by 🤖 GitLab Bot 🤖's avatar 🤖 GitLab Bot 🤖

Add latest changes from gitlab-org/gitlab@master

parent a264dc20
......@@ -23,7 +23,6 @@ class List < ApplicationRecord
scope :preload_associations, -> (user) do
preload(:board, label: :priorities)
scope :ordered, -> { order(:list_type, :position) }
title: Fix missing board lists when other users collapse / expand the list
merge_request: 17318
type: fixed
......@@ -5,8 +5,8 @@
> Docker versions earlier than 1.10.
NOTE: **Note:**
This document is about the admin guide. To learn how to use GitLab Container
Registry [user documentation](../../user/packages/container_registry/
This document is the administrator's guide. To learn how to use GitLab Container
Registry, see the [user documentation](../../user/packages/container_registry/
With the Container Registry integrated into GitLab, every project can have its
own space to store its Docker images.
......@@ -137,7 +137,7 @@ from io import BytesIO
s3_file = requests.get(presigned_url)
url = ''
files = {'file': BytesIO(s3_file.content)}
files = {'file': ('file.tar.gz', BytesIO(s3_file.content))}
data = {
"path": "example-project",
"namespace": "example-group"
......@@ -4,8 +4,7 @@ type: reference, howto, concepts
# Subgroups
NOTE: **Note:**
[Introduced]( in GitLab 9.0.
>[Introduced]( in GitLab 9.0.
Subgroups, also known as nested groups or hierarchical groups, allow you to have up to 20
levels of groups.
......@@ -68,9 +67,9 @@ Another example of GitLab as a company would be the following:
The maximum subgroups a group can have, including the first one in the
hierarchy, is 21.
Actions such as transferring or importing a project inside subgroups, work like
when performing these actions the traditional way with the `group/project`
When performing actions such as transferring or importing a project between
subgroups, the behavior is the same as when performing these actions at the
`group/project` level.
## Creating a subgroup
......@@ -117,6 +116,10 @@ When you add a member to a subgroup, they inherit the membership and permission
level from the parent group. This model allows access to nested groups if you
have membership in one of its parents.
Jobs for pipelines in subgroups can use [Runners](../../../ci/runners/ registered to the parent group. This means secrets configured for the parent group are available to subgroup jobs.
In addition, maintainers of projects that belong to subgroups can see the details of Runners registered to parent groups.
The group permissions for a member can be changed only by Owners, and only on
the **Members** page of the group the member was added.
......@@ -94,8 +94,8 @@ module QA
# replace with (..., page = self.class)
def click_element(name, page = nil)
def click_element(name, page = nil, text: nil)
find_element(name, text: nil).click
page.validate_elements_present! if page
# frozen_string_literal: true
require 'securerandom'
module QA
module Resource
class Issue < Base
......@@ -20,6 +22,7 @@ module QA
def initialize
@assignee_ids = []
@labels = []
@title = "Issue title #{SecureRandom.hex(8)}"
def fabricate!
......@@ -27,10 +30,10 @@ module QA
Page::Project::Issue::New.perform do |page| # rubocop:disable QA/AmbiguousPageObjectName
Page::Project::Issue::New.perform do |new_page|
......@@ -59,9 +59,10 @@ module QA
def click_element(name, page = nil)
def click_element(name, page = nil, **kwargs)
msg = ["clicking :#{name}"]
msg << ", expecting to be at #{page.class}" if page
msg << "with args #{kwargs}"
log(msg.compact.join(' '))
Markdown is supported
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