-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
Hello, I am observing an unexpected (but, as far as I can tell, correct) behavior with the GitCopyDiff devops pipeline activity.
- branch 1 diverges from master and changes are made on the branch
- branch 2 diverges from master and changes are made on the branch
- branch 2 is merged back into master, triggering the pipeline
- the build artifact for branch 2 is generated and contains only files that were changed in branch 2.
- branch 1 is merged into master, triggering the pipeline
- the build artifact for branch 1 is created and contains all changes from branch 1 and branch 2.
The issue is avoidable by merging master into branch 1 before merging branch 1 into master.
Is there an argument that can be passed to GitCopyDiff that will cause only the changes from branch 1 to be included in the build artifact generated in 'step 6'?
If not, could I submit a PR to include that feature?
Thanks for your time!
Metadata
Metadata
Assignees
Labels
No labels