Problem Definition

The condition - changesets - includePaths option in Pipelines takes into account at the moment only the last commit pushed, for pipelines other than pull-request ones.

When someone makes a push consisting of multiple commits, only the last commit will be taken into account for e.g. a branch pipeline.

This is not always desirable. If 5 commits are pushed, the last one may not have any changes in the directories/files defined in includePaths, but the previous ones may do. There are some users that would like to have the pipeline triggered in this case.

Suggested Solution

It has been requested that the condition - changesets - includePaths option takes into account all commits since the last successful build, for pipelines other than pull-request.

Workaround

One way to work around this at the moment would be by pushing commits one at a time.