Hi everyone,
I was exploring the metadata validation workflow and noticed that it currently runs only when changes are made inside modernization-metadata/.
I had an idea to slightly improve this by expanding the trigger paths so that validation also runs when other important metadata-related files are changed — specifically opt-out-plugins.json, since it directly affects which plugins are included in automation.
I haven’t opened a PR yet — just wanted to check if this approach makes sense before proceeding.
I also considered including the reports/ directory in the trigger, since it contains aggregated data used by dashboards and other tools. But I’m a bit unsure here:
-
since reports are derived, is it necessary to validate them?
-
or should validation stay focused only on source metadata?
Would love to get your thoughts on this before I move ahead and open a PR.
Thanks!