In gitlab, I have a team member who has the general role of developer. I'd need to make him a maintainer for a specific project. I've looked through the documentation but I'm not finding a strait forward answer on how to upgrade his role in the specific project.
I suggest you have to remove the member from group and add him/her to individual projects with a role(maintainer for "Specific project" and developer for other projects in your case).
Thats the temporary solution I found
Related
I have this workgroup and I would like to make lists of interesting projects/repos contained in different subgroups. This would make it easier for us to find relevant projects.
I know you can share a project with a group if you are the owner of that project but can I, as maintainer of a group, add links to public projects without the owner of that project having to do anything?
Another option for me could be to just do a readme file with links but then I could get dead links and I would miss the project description and most importantly, when they last was updated.
This does not 100% qualifies as an answer, as i see it as a hack or misuse of a feature of GitLab. But i thought the idea is worth sharing. Additionally it will only work with projects which you can actively change - else this would need interaction of project maintainer.
GitLab supports optional topics on projects, they can be maintained by maintainers within the general settings of a project.
If you add a topic interesting. they get searchable by this tag like https://gitlab.com/explore/projects?tag=interesting
This way, you can create and maintain a list, which is always up to date and show the most recent description, name, etc. - also in connection with permissions (you will not see something you are not suppose to see).
The downside is, that this topic might not be suitable to be (ab-)used within your group, and it might add more confusion for others than it should, because you will see this topic in the project overview page.
Currently I have an GitHub repo that I use for collaboration. I want anyone to be able to join it.
GitHub currently requires users to first find me (there is no form to request) and ask me and then they are mailed an invitation which they then have to accept.
I'm guessing there is an app out there for this but I can't find it.
I'm looking for either an integration that takes a turns a issue comment into a team add, or form the user can request an invite from.
Forking a repo remains the official way to contribute without asking. Then the contributor can make a pull request back to the original repo.
The goal is to "manage" (through PR review) the flow of contribution.
The other alternative would be to add several people owner of an organization team: that way, you would be the only one people would have to ask in order to be collaborators.
If this is an organization that you're trying to add members to, there is already some automation around that.
JazzBand allows anyone to join the organization. Their website uses the same mechanisms as add-to-org to add people to an organization.
Looking at their source code, it appears both use the GitHub API to add members to an organization.
PUT /orgs/:org/memberships/:username
That said, if this is a personal repository, you'll instead want to follow the API to add a collaborator
PUT /repos/:owner/:repo/collaborators/:username
It's likely you could modify either of those projects to fit this need. Cheers!
We have a project administrator for a collection of projects on TFS Online. We recently hired so he had to add the guy as a new member into the team.
However he cannot see one specific project we have, even with identical permissions as the other users. His account was created in the same way as the others.
Trying to help the guy out here I offered to try a few things and noticed, If I create a new project as a test. "Test1", and add him as a member, he can see this account fine when he logs in to TFS Online/Connects on Visual Studio.
Which leads me to believe that it's based on some visibility setting within TFS, even though the other members linked to the project can see it fine.
Any possible ideas for me to try?
You need to try and trace his effective permissions. It sounds like there is a denied somewhere.
If you open the admin for that team project and goto the security tab there is a box to add the users account. You should then see the effective permission on the right and he should have and Alowed in the "View project level information" permission.
If he does bot you can roll your mouse over it and click the "why" button and you will see where the overide is coming from.
I am using TFS 2012/VS 2012.
I have five work items available to me: Bug, PBI, Task, Test Case and Impediment. I cannot figure out how to access user stories, and none of the information put out by Microsoft is very helpful.
I suspect the template that was used to create my project did not include them, but I am not sure. Is this true?
Can I alter my existing project to add user stories or requirements?
When creating a new project, which templates will automatically contain user stories or requirements?
Looks like you used the Scrum Template to create your Team Project. Only the Agile Template includes User Stories by default.
You can use the witadmin.exe tool to add additional Work Item Types to an existing project.
In Scrum PBI is the equivalent of a User Story (and in CMMI the Requirement is the equivalent of a User Story).
I have two security roles ProjectLead and Developer ; also I have one custom entity named Project. Is it possible that ProjectLead and Project have 1:N relation(one ProjectLead can work in more than one Project)
and Developer and Project have 1:1 relation(one developer can work in one project)?
Thanks.
I don't understand your problem. You want make relationship between a role and a entity, this ins't possible and don't make any sense. You want restrict the access to projects? This can be done with roles, in Developer role for project entity you can put the read action in user option (just one level) like that the developer only viewed that project or if you have a team with many developers you that team can own that project.
For ProjectLead you can put access at Business unit level.