I need to deny creating pull requests into specific branch for a certain group of users.
They are already set as a group in TFS, that group has been set "Deny" permission for "Contribute" to that specific branch - however its members are still able to create pull requests.
Am I doing something wrong?
Users with "Contribute" permission in a branch can push new commits to the branch and lock the branch. This permission doesn't control creating pull requests.
There is no permission to control creating pull requests on branch level, you can only control creating pull requests on Repo level, check the following screenshot:
You can only use branch policy to protect your Git branch, but deny creating pull requests into specific branch is not an option.
Related
Bitbucket has a remote merge facility. In the event that a target branch already contains the commits in a pull request, the PR will be remotely merged. I would like to determine which pull requests contain a commit so I can determine which approved pull requests led to the remote merge status.
From the API docs, I can use GET /rest/api/latest/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}/commits to identify the commits. Is there a reverse operation that shows pull requests for a specific commit?
I am not finding the info in the API page here: https://developer.atlassian.com/server/bitbucket/rest/v807/
I have question on ADS GIT Pull request permissions Is there any way to prevent others from being able to change the status your pull request? like being able to publish your draft request, setting the complete status, abandoning etc?
Is there any way to prevent others from being able to change the status your pull request?
Sorry for any inconvenience.
Now, Azure devops service/server doesn't provide a feature to meet this requirement.
To protect the Pull Request, you could add reviewers for the target branch to prevent set the complete status directly.
On the other hand, we could set creator's target branch or repo contribute permission to Deny, you need to add specific user to target Branch security page. This not applied to all the creators all the PRs. Just a specific PR and specific user:
But none of these settings apply to abandon. For this option, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
Hope this helps.
I am really lost in my GIT today (and a newbee too)
I have 2 bitbucket users, and with user A I created a private repository online on the bitbucket site.
I've been pushing source changes to it, and all is well. (both via sourcetree and from the command line)
Until... I saw that the user pushing the changes is user B (I once created two accounts for bitbucket), and I did not grant him rights.
I probably am doing something wrong here, but I want to understand what that is.
When I do git config user.name I get 'userb'
When I look at the raw commit in the repo I see 'userb'
I have the access level : private repository
I did not send any invitation (afaik)
I don't know If I've ever granted userB all access to userA (Is that possible, and if so, where can I see that?)
When I look in the config file in the .git directory, I see no username
Is the user that pushes the code maybe another one then the committing user? Can it be that userB edits and commits, and userA pushes?
I don't think I've just experienced a security leak, but I do like to know why this happens.
Our company is using Team Foundation Server 2015. Is it possible to add one or several persons automatically as reviewers to every pull request? As required default reviewers?
Yes, you can add default reviewers to pull requests quite easily.
If you configure your branch policy you can have different reviewers occur for different code paths. If you want to add default reviewers to all pull requests for that code path you can specify "/*" in the path box. They will then be added to every pull request.
We are developing a replica of Jenkins and we have a need to authenticate SVN & GIT repository URLs. I see Jenkins is able to do it through allowing the user to have credentials created(POST) and validated through(GET) a call. However, I am unable to validate the SVN/GIT repo without the jobname.
I am able to fetch the global credentials added to Jenkins. But they are only retrieved for job basis. So if I want to see the list of credentials of a particular job, I can do it using the following JSON.
http://${JENKINS_URL&PORT}/job/${JOB_NAME}/descriptorByName/hudson.scm.SubversionSCM$ModuleLocation/fillCredentialsIdItems
But I would like to fetch the credentials without depending on the job name. Please let me know if I have to provide any more information. Any help is much appreciated.