A group is a collection of repositories. You can manage permissions for repositories in a group by configuring members. Groups also support subgroups for structured project organization.
Create group
-
Log on to Alibaba Cloud DevOps and click Codeup in the top navigation bar.
-
In the left-side navigation pane, select Groups, and then click Create Group.
-
In the Create Group dialog box, enter the following information:
-
Group Name: A name for the group.
-
Group Path: Defaults to the group name.
-
Group Description: Optional.
-
Visibility: Sets the visibility of the group within your organization.
-
-
Click OK. The group is created.
View group
-
Subgroups and Repositories
On the Subgroups and Repositories tab, you can create subgroups, import repositories, and view all subgroups and repositories in the group.
A subgroup is also a collection of repositories created under a parent group. You can have up to four levels of subgroups.
On the Subgroups and Repositories tab, you can also click New repository to create a new repository.
-
Merge requests
Lists all merge requests for the group and its repositories.
-
Activity
Displays recent activity across the group, its subgroups, and repositories.
Activity includes member activity, commit activity, and merge request activity.
Members
You can assign and adjust member roles, add members, and remove members to control permissions for your groups and repositories.
In the left-side navigation pane of the group, click Members. This page lists the current members and their roles, such as administrator and developer. You can use the search box to find members by name.
Settings
Basic settings
As a group or organization administrator, you can modify basic group information, including the name, description, cover, and visibility.
At the bottom of this page, the high-risk operations section provides three options: Modify Group Path (changes the group's URL path), Transfer Group (moves the group to a destination group), and Delete Group (moves the group to the trash, where its data is retained for up to 15 days).
The visibility of a group affects its subgroups and repositories as follows:
-
If a group is public, its subgroups and repositories can be private.
-
If a group is private, its subgroups and repositories must be private.
-
If a group is private, you can change it to public.
-
If a group is public, you can change its visibility to private only if all its subgroups and repositories are also private.
The rules above apply only if your organization's settings permit such changes. If not, the settings defined at the organization level take precedence.
High-risk operations
-
Modify Group Path: Developers often access resources by entering a URL directly. A meaningful path helps them find repositories faster. After modifying the path, you must update the remote URL in your local repository to point to the new address.
-
Transfer Group: Transfers a group to another group. The original clone URL becomes unavailable after the transfer. You must update the remote URL in your local repositories to point to the new address.
-
Delete Group: Deleting a group also deletes all of its subgroups and repositories. These items are moved to the trash and can be restored within 15 days.
Webhooks
A webhook calls a specified URL when a specific event occurs. Supported events include push events, comments, and merge request events. For example, a webhook can trigger a continuous integration (CI) build, perform an image backup, or initiate a deployment to production.
A webhook configured at the group level is inherited by all repositories in the group. It cannot be edited or deleted from within a repository. To modify it, go to the group's settings.
On the Settings > Webhooks page of a repository, you can view the list of webhooks inherited from the group. In addition to the inherited event types, repository-level webhooks also support tag push events. Click + New Webhook in the upper-right corner to create a new webhook.
After a webhook is configured, you can listen for repository events. For details about the message body, see Webhook settings.