Pipelines with `include` triggers all ran when an empty commit was made #45

[ssaitta]

Observed Behaviour

I recently made an empty commit and our pipelines triggered by include clauses all kicked off. This was problematic for us since we have production infra pipelines which we did not want kicked off at that time, and could have caused outages for us.

Steps to Reproduce

1. Include a path include trigger on your pipeline.
2. Push a commit with no files.

Expected Behaviour

I would expect pipelines triggered by include clauses to only go off if that path name is matched by a changed file, so no include pipeline should run.

I saw this bug report from 2 years ago and this issue is basically the opposite case. The author of this bug report says "The pipeline should run, since none of the files didn't match (can't exclude nothing)." and we have the case where no files were included so the pipeline should not run, since none of the files were included.