pull request email notifications, triggered before code is in the target repo

I wanted to do some of my pull-request reviews locally. Then run tests and such forth

So naturally i get an E-mail for the pull request, so i tried to do the following:

 git fetch --tags origin +refs/pull-requests/*:refs/remotes/origin/*

This works when the pull request is created, however when the pull request is updated I get the e-mail telling me but when i re-run the git command to fetch it locally it does not appear in the repository.

It only updates the repo when i view the pull request in my browser, this seems to defeat the point of having a notification.

 

Is there a reason the pull request notification is triggered before the refs/pull-request/ID is updated ?

 

 

1 answer

This is by design, the merge to +refs/pull-requests/* is not done because it's expensive to do on the Bitbucket server for every commit on every to the source or target,

 

Therefore it's only done when the pull request is viewed in the UI of bitbucket.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

2,026 views 1 5
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you