You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love to be able to easily connect SQLFluff or another linting tool that only checks for files that are about to be deployed (rather than scanning an entire codebase).
It technically would be possible to parse the dry-run output and look for "Applying change script..." However, it only outputs the file name, not the entire path to the file which would be beneficial to use in other actions (linting, etc.).
Not sure if others have tried something similar, but I would be willing to take a stab at the code if others think this is a good idea.
The text was updated successfully, but these errors were encountered:
I would love to be able to easily connect SQLFluff or another linting tool that only checks for files that are about to be deployed (rather than scanning an entire codebase).
It technically would be possible to parse the dry-run output and look for "Applying change script..." However, it only outputs the file name, not the entire path to the file which would be beneficial to use in other actions (linting, etc.).
Not sure if others have tried something similar, but I would be willing to take a stab at the code if others think this is a good idea.
The text was updated successfully, but these errors were encountered: