Old state of target branch in pull requests

Copper Contributor

Dear all,


we have encountered a strange behaviour when doing pull requests in DevOps.


If we create a new feature branch A from target branch B, make some changes in both branches (A and B) and finally, try to merge the updated feature branch A into target branch B via pull request, the change management tools/views in pull request in DevOps will consider state of target branch B before forking.

From our perspective, this is not expected behaviour and requires additional step: merging latest target branch B into feature branch A.


Have you experienced similar? What is your opinion on this matter?

0 Replies