Kursat Topcuoglu

@XiChu2333, thanks for this patch. Did you consider using sqlFluff's [--write-output](https://docs.sqlfluff.com/en/stable/cli.html#cmdoption-sqlfluff-lint-write-output), instead of `>>` ? In my project, we have a few configurations which don't apply to any resources; thus,...

hey @jakub-auger, we workaround this by schema level with overriding `spark__create_schema` macro like; ```sql {% macro spark__create_schema(relation) -%} {% set s3_path_pattern = '^s3://([a-z0-9-_]+)/([a-z0-9-_]+)/$' %} {%- set s3_schema_location = var("default_schema_location_root") ~'/'~relation.quote(schema=false)~'/'...

@jakub-auger , lastly, are you able to remove `stale` label from this issue?

hey @benc-db , We don't see the error on Delta sources. And it's not a column modification issue. Table metadata stays the same. Here is the whole story. **Steps To...

hey @GeekSheikh, We're using SQL Warehouse (classic) in our environment (aws), unique custom tags assigned to SQL Warehouses and I believe we're able to get our SQL Warehouse dbu costs...

hey @yu-iskw , do you have a chance to test the same scenario with the `dbt` templater, instead of `jinja`? `INPUT_WORKING_DIRECTORY`: https://github.com/yu-iskw/action-sqlfluff/blob/2b313f10cc5db392bed833c57b7bac89775b2597/action.yml#L155 my hypothesis is, as we're CWD to `INPUT_WORKING_DIRECTORY`...