Forum Discussion
Old state of target branch in pull requests
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?
1 Reply
Take this:
- Regularly merge or rebase the target branch (B) into your feature branch (A) before creating or updating a pull request.
- This ensures the PR reflects the most current state of B and avoids integration issues later.
