I noticed strange diff view on pull request.
Here is example: yt-94 was branched from yt-98 and preparing for pull request.
If destination branch is yt-98, than diff view is correct.
94 into 98.png
But, if destination - is new yt-94 branch (for origin), than diff view shows changes, that does not exist in the source commit:
94 into 94new.png
Is it possible to change this?
No, I did not merge yt-94 into yt-98, because it was made for example. I already had such pull request, merging it ends correct, but code review in quite tricky - that is the main problem. I also found, that this happening after comparing fork and origin and merging changes from origin to fork. With "clean" fork diff view is right.
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