currently Go merges multiple modifications of a material for scheduling pipeline.

So if pipeline A watches git repo G and the last run was for g1. Now there are 3 new commits into G - g2, g3, g4. Go would schedule A be merging them into one instance, thus saving time.

But sometimes it would be useful to force Go to schedule 3 different instances of A (1 for each change)

This will be useful to support feature-branch / PR build plugins. reference