I have a Gitlab group (testgroup) also I have the project (testproject). Now the testproject is in the testgroup.
What would happen if I added A group (testgroup) master as a developer in the inside of the project?
Would they able to accept the merge request for the particular project?
How could I add the group master as a developer in the same group's project?
Someone who is declared a group master is not a project Master, even if that project is in the group
See Group permission: he or she only has the additional privilege of creating projects in the group.
Related
I have created a release pipeline with multiple stages. Now I would like on users form the Release Manager group or Project Administrators group to be able to deploy some of these stages.
I have tried to denied "Manage Deployments" to the other groups but it seems as soon as Contributors lose this, no one, not even members of the above groups with the permission set to Allow can deploy the stage anymore. BTW, members of the allowed groups are also members of Contributors.
I tried both just updating the permission and removing Inherited permissions and then removing the permission for those groups and still no go.
Is there any way to remove this permission from Contributors but sill allow members of Contributors + Release Manager + Project Managers to deploy?
Thank you
Is there any way to remove this permission from Contributors but sill allow members of Contributors + Release Manager + Project Managers to deploy?
I could reproduce the scene you mentioned. It seems that the permissions of the Contributors group will override the permissions of the other two groups.
To solve this issue, you could set the Manage Deployments as Not Set instead of Deny. At the same time, you need the disable Inheritance option.
Note: If you set Not Set, people in the contributor group cannot deploy, but if some of them are in other groups with this permission, they will inherit the permissions from other groups
We have an Azure Devops Project with several repositories.
However we only want to give access to a couple of repos to another team.
I've setup a group called Outsource (oddly it doesn't show under Project Settings > General > Teams) and within the Project Settings > Repos > Repositories section i've given the group permissions.
However they can't access theses repos from My Org > Repos (red icon).
Also they can't clone the repos either.
The one user in the 'Outsource' group is setup as a basic user.
Can anyone tell if I'm missing a setting? It doesn't seem like providing permission against a repo does anything?
I also gave them access to a different project and they can access that fine.
Stakeholder user cannot access private project repo.
The permission group Outsource is collection level group, we recommend that you open the project settings and create a project level permission group and add these users.
Configure permission
Open project settings-> Repositories->click one repo-> select the repositories which you want to give access to another team->add the permission group and set the permission Read to Allow. Then the group users can access these repositories.
Select the repositories which you do not want to give access to another team->add the permission group and set the permission Read to Deny. Then the group users cannot access these repositories.
As a group owner in gitlab, i want to fork a project in the group namespace into my own user namespace. But when i open the project page in gitlab, i dont see the fork option on the page. How do I then fork the project ?
In our organisation we recently moving to git, I have created a group accidentally I would be appreciate if there is a way to delete this group.
In the most recent version (Mar. 2019):
At top bar, click on Groups.
Type part of the name of the desired group or click on Explore Groups. Click on the desired group.
Go to Settings > General
Expand Path, transfer, remove
At the bottom of page you find Remove group. Click on the button and type the name of the group to activate Confirm button. Then click on Confirm to delete the group.
On the recent version (per posting date 11.4.4) navigate to your group's
Settings > General > Advanced > Expand
There you will find the Remove group button.
The group deletion has changed with GitLab 14.8 (February 2022)
Delete groups at the parent group level
In this milestone, we’ve worked on one of the initial steps to reach feature parity between group owners (in any installation base) and administrator-only functionality that exists solely in the administrator panel for self-managed users.
Group owners can now delete a group and its subgroups from the parent group level. Until now, group owners had to go into each individual group to delete them, which was timely and inefficient. Group owners can now view all groups and delete them from a single place.
See Documentation and Issue.
Note: GitLab 15.4 (September 2022), but only the non-free version, comes with:
API support for immediate group deletion
You can now use the API to immediately delete individual subgroups. Prior to this release, you could only delete individual subgroups from group settings in the UI.
See Documentation and Issue.
Using the latest GitLab API, I checked the project team members of a just created project in a group... and it's an empty Array which is returned
#git_repo_client.team_members(19)
-[]
Previously to this test, I created a group and added members ( master permission so they can create projects in this group )
Then I created projects inside this group
why these group members are not set as project team members ?
should I also add them via the API ? or did the project team methods are deprecated in this latest version GitLab 7.10.1 d5c71c8
thanks for feedback
finally, I decided to duplicate the group members into the project team members within my script ... seems to be 2 different sets