Clean-up excess includes for triggers. #13970
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is more for discussion than anything else at this point. I was helping out the management plane team with a new pipeline an observed that the
ci.yml
file they were using had some extra path filters fortools/
,sdk/core/
, andeng/
. It wasn't for all service directories and it got me thinking if it was intentional or not.Do we still need these triggers, especially on
eng/
. When sync PRs are pushed this has the potential to really hammer the build pools with this broader coverage created by the triggers.