Handling whitespace in sql formatted changelog

Recently, we noticed some changesets landing in the databasechangelog with ID’s ‘raw’ and author ‘IncludeAll’. After investigating we noticed that white space at the top of the changelog files was the culprit. We were super happy to know that the sql applied without issue. However, is there a setting to ensure that if one were to validate the sql file it would know that the whitespace would cause this issue (or some other existing solution that would clarify any confusion on my end :smiley:)?

Team is aware and we have modified the workflow to ensure that the whitespace doesn’t make its way in again.