Is it possible to trigger some action after completing a pull request in TFS ?
Let's say for exemple that a product backlog item is attached as a "related work items" in a pull request.
Could you change it's state automatically after validating the pull request ?
This can be achieved using TFVC as source control. Work item will be resolved after the check in action. However, it's not support for GIT in TFS now.
You can submit a feature request in uservoice, TFS admin will kindly review it：
Uservoice Site:
https://visualstudio.uservoice.com/forums/330519-team-services
Related
A team member made a pull request using TFS. And completed it, but we want to revert it. When clicking on revert we get this message.
I have this message Pull requests must be completed and not externally merged before they can be reverted
I'm using Microsoft Visual Studio Team Foundation Server Version 15.112.26307.0.
Using the Releases page/view for a group of approvers to review and manually trigger the release from environment QA to environment PROD (first environment triggers automatically).
From that screen, the approver clicks the icon and then in "override" to approve and launch second environment... on that action (popup) it asks for a comment and the the user clicks the approve button which triggers the next release environment... until here, its the standard way from TFS....
I wanted to know if there is a way to list all releases that completed all environments, and on that list show who approved it and also the comment entered... is it possible to customize a view or create a whole new list querying that information? Its a information/audit list only... no need to take action from there... just summarize the information for review.
Thanks!
You can use Releases - Get Release API to get the information you want. Since you are using TFS 2017 Update 1 RTM, you could capture the rest api by pressing F12 in browser then select Network. Check the screenshot below:
I've tested the following api in Version 15.117.27414.0, and get the comments successfully:
Get
http://tfs2017:8081/tfs/{collection}/{project}/_apis/Release/releases/{releaseId}
We have TFS 2018 Update 3. We have git repositories and branches on them are secured with branch policies.
We have TFS groups which are through branch policies used as default approve groups for pull requests.
Problem: when somebody creates a PR to a particular branch, we'd expect, that people in the default group receive an email from TFS that new PR was created.
Despite the fact, that all of them have their own notifications enabled, they do not receive it...
Is there any configuration I need to do?
You need to configure the notification in the Team level:
I already merged a pull request in bitbucket. Can you all explain what is the difference between click Approve and don't click it?
Because I see that the merge commit still appears in git history/log even that I don't click Approve.
If your team has a Premium plan, repository admins can prevent pull requests that don't have a certain number of approvals from merging.
Other than that, it is a visual check only that the merge request was reviewed and approved prior to merging.
See: https://confluence.atlassian.com/bitbucket/pull-requests-and-code-review-223220593.html
We have a setup with Bitbucket GIT linked to JIRA issue tracker. It is possible to add special comments to GIT commit messages to update JIRA issues automatically.
However, is it possible to put the link to the Pull Request, when it is created, to the corresponding JIRA issue? JIRA issue knows the name of the branch, so it should also have information on the pull requests.
If you reference your issue keys in your commit messages, branches and pull requests then this information will automatically appear in your issue's development panel.
This requires that you have an application link configured between JIRA and Bitbucket.
This is how it should look:
More info is available on the Development Information documentation page.