I opted for admins to be added as "owners" instead of "masters" because project masters can managers members, but only group owners can manage members.
add rake gitlab:import: all_users_to_all_groups and user_to_groups
Coverage remained the same when pulling 1710503 on gabetax:rake_group_bulk_add_permissions into 4c47a89 on gitlabhq:master.
@dosire What do you think about this PR, wont this change intended behavior?
@jvanbaarsen It seems to be new behaviour that is documented properly. @randx what do you think?
@randx Can you take a look?
@jacobvosmaer Can you take a look?
Is this necessary? I thought admins can do what they want, whether they are 'Master' or 'Owner'.
@jacobvosmaer Well, if i remove your admin status, you wont be able to manage te users (I think thats the reason for this PR)
I wrote this for myself because I have 100+ "private" repos over 10 groups with 25+ users. I want most of my users to access most of my repositories, so I'd rather start with a mass grant, and then manually pare down access as necessary. I don't want to achieve access using the "internal" visibility setting, because I will inevitably have to add an account for an external vendor or consultant at some point. The current two ways for me to achieve this are:
As for the "owner" flag given to admins, I did just confirm global admins can still manage group members (except for their own) even if their group-level access is only 'developer', so I'm open to whatever access level makes the most sense, but adding them as owners is not giving them any added permission they wouldn't otherwise have.