It is possible to set branch policy to require comment resolution before pull request can be completed. However, it seems that anyone - not just the comment author - is able to set comment status to "Resolved" and therefore complete the pull request effectively circumventing the policy.
Is there a way to restrict that and configure the system so that only comment author is able to set it's status to "Resolved"?
Related
We use Jira to handle client issues. When a customer raises an issue, as the first response for issues, we changes issue status into "In Progress" and send reply to customer. I need to automate this procedure.
You may use Jira Workflow post functions to set specific actions that Jira should do when some issue changes its Status.
Here is more details on this matter: https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
Also, you may search for the 3rd party Jira apps that add extra automations here:
https://marketplace.atlassian.com/search?query=automation
Thanks,
Oleh
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.
Gerrit allows associated external changes into a single change request via "Depends-On" on the commit message. However, by the looks of it, rest api does not expose these dependencies.
I can ofcourse get the commit message and then parse it, and then get change request for this external change.
Anyone know if there would be a bit more streamlined option to archive the same ?
You can get the related changes using REST API:
'GET /changes/{change-id}/revisions/{revision-id}/related'
Retrieves related changes of a revision. Related changes are changes
that either depend on, or are dependencies of the revision.
Request GET
/changes/gerrit~master~I5e4fc08ce34d33c090c9e0bf320de1b17309f774/revisions/b1cb4caa6be46d12b94c25aa68aebabcbb3f53fe/related
HTTP/1.0
See more info in the Gerrit documentation here
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.
my team and I are using Team Services with Visual Studio 2015. I understand the concept of a pull request, but the rejection and correction process is very blur.
MSDN falls short of covering this part on the main page regarding the topic: https://msdn.microsoft.com/en-us/library/vs/alm/code/git/pull-requests
Basically, when you reject a pull request, what's expected of the person that created it? Should he modify his branch and issue a new different request? or bring changes to his branch in a way that will make it appear under the current request? In the latter case, how?
Thanks
More detailed description is placed here: Conduct a Git pull request on Visual Studio Online
Make changes on the source branch
To act on the feedback, the requestor revises the code on their dev
machine and pushes the changes so that reviewers can see them.
So the requestor need to update his code and push the changes into source branch. The code in the pull request will be updated automatically after new change is pushed.