I want to update my own comment for a commit in the check-in history but I receive error as snapshot as below.
I understand that my account is not an admin/owner of the repository but it should be allowed me to update my own comment! On TFS side, I can do this actually.
Is there any work-around for me? I don't want to provide admin right to all users.
You don't have to give every user admin rights. But the error returned by your pre-revprop-change hook script tells you that only admins or project owners can change log messages.
So either change your pre-revprop-change hook script to allow all users to do that, or add yourself to the owners group or admin group.
Related
I cloned a workspace in perforce from other credentials (as i was having some issue with my account back then due to permissions). Now i have the relevant permissions so want to change the owner of that workspace.
In p4v tool, I logged in from the account through which the workspace was created and i tried to change the owner in the advanced options but it gives an error "Client specification failed: You can't create another user's workspace."
Any ideas on how can we change the owner ?
I'd recommend using the command line as it's much faster
p4 client <workspace name>
Then change the Owner: to the one you want, save and you're done.
Another project that was created directly in the organization shows me as owner.
Is there a way to fix this in the settings?
I checked the settings/members page, and the only way I see is to click the "Leave" button next to my maintainer status, and then hope that I will automatically be marked as the owner.
The short answer is yes, that's safe to do.
When you transfer a project, all roles are kept "as is". Since by default, you're a Maintainer on the personal project, when you transfer it, it keeps that role for you.
When you have a role in the group, it will inherit the role, unless a role is specified for the project. By deleting your role at the project level, you're just deleting the specified project-specific role. Once you do, you should show up as an Owner (inheriting it from the group).
I want any user in our Group that created a new repository to automatically have maintainer rights for that repo.
I can't find any administrative settings on Gitlab.com that would imply the ability to do this automatically.
I have all users in the group set to "Developer" privileges on all repos but I'd like to have the user that created the repo to be set as "Maintainer" upon repo creation.
I haven't tried this, but here is the idea.
Setup a System Hook for project_create event:
https://docs.gitlab.com/ce/api/system_hooks.html
https://docs.gitlab.com/ce/system_hooks/system_hooks.html
In hook body owner_name is hopefully the creator.
So in your script you can then make an API call to promote user:
https://docs.gitlab.com/ee/api/members.html#add-a-member-to-a-group-or-project
We have an issue. User is in the Contributors group of the VSTS project. Able to view dashboard and work items. Unable to view Repos. Need help. Any suggestions?
User needed an MSDN license to use Visual Studio in addition to being in the correct group of the VSTS project. Trial license was not good enough.
According to your description, highly doubt those users only have Stakeholder access level.
People with Stakeholder access level could not commit their work on branch and unable to view repos.
Assign Stakeholder access to those users who need to enter bugs,
view backlogs, boards, charts, and dashboards, but who don't buy basic access. Stakeholders can also view releases and manage release
approvals. Stakeholder access is free.
Source Link: About access levels
See Stakeholder access for details of features available to stakeholders.
The user should have either Basic access or Visual Studio subscription which include code feature.
Moreover, if it's still not able to see any other projects after giving them those access. There is another concept called Permissions in Azure DevOps. Double check the permission for Contributor group.
Also make sure you have not add them to any other project team group expect the contribute group.
Once deny the Read permission for repos level, user will not be able to see the repos.
Read
Can read the contents of a file or folder. If a user has Read
permissions for a folder, the user can see the contents of the folder
and the properties of the files in it, even if the user does not have
permission to open the files.
i am using Drupal 6.x
I had created two users i.e. a user with all permission i.e. Webmaster and other is member. The permissions of member are restricted and are allowed only to create story, delete own story and edit own story. However when i logged in with member name i got only three option i.e.:
My account
Create Content
Log Out
The post submitted by that user is not visible. I want to display all post published by that user in its account detail, and here he/she can easily edit, delete or modify his/her content. How it can be possible. Have you any idea. If yes then please guide me step by step. waiting for your reply. Thanks in advance for this support.
This is because of permission issue, steps to solve this issue
Create a view to list the story with edit button.
Go to the admin/user/permissions and give create, edit and view permission for the user.
publish the created article via admin user.
Last assign the created view block to users home page.