The way to do this properly would be to have your developers do their work in feature branches and for each branch there is a pull request which is approved by someone who then merges it back to master. (Most developers would not have push rights to master, set this in branch permissions.)
The pull request contains all these and a very nice interface to handle the review on the server, no plug-ins needed. What do you want to do with this data?
Evrybody who is added as a reviewer to a pull request, will receive an e-mail with the following:
- Name of the pull request
- Who created it
- Which branch will eventually be merged to which other branch
- List of commits (with links to each)
- A button to view all details of the pull request on the web interface.
I think this is exactly what you want. :)
[You can test the whole workflow if you create two test users and create a pull request with one, assign the other as reviewer.]
Oh is it, Actually now I'm having local stash server but I didn't configured the e-mail.
earlier this [You can test the whole workflow if you create two test users and create a pull request with one, assign the other as reviewer.] test case I did.
I'l try to configure the email locally and il tell u.
One doubt reviewer will come to the picture with pull-request only?..
A pull request is not only a tool for code review, it is also a tool for discussion. It can be created as soon as the branch has at least one commit in it (and it gets updated each time there are additional commits). So if you need the reviewer to come into the picture earlier than the finishing of the task/feature, you can instruct the developers to create it at an earlier point.
(I leave this up to them. Most of the time they only want CR when done, but they are informend that they can create the pull request before as well, if they need advice/discussion.)
About the data in the merge check: I have never done this, but once you get the pull request object, it looks like you can query all the parameters from it: https://developer.atlassian.com/static/javadoc/stash/latest/api/reference/com/atlassian/stash/pull/PullRequest.html
I able to configure the mail and after adding the reviewer I able to get the mails.
with some hook I need to capture the
name of the developer who gievn the pullrequest,
I need to capture.
I have gone through RepositoryMergeRequestCheck and MergeRequestCheck.
Able to get the reviewers names and updated date and other above details I didnt get.
How can I achive all the details.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot