atlas conflict with ban-concurrent-index-creation-in-transaction

[jay-babu]

When adding this comment in atlas: https://atlasgo.io/versioned/apply#file-level-transaction-mode, it disables transaction mode. However in squawk, I have the flag enabled for assume in transaction, which causes this issue where transaction is disabled with the comment, but squawk believes it is real as it is unaware of atlas's comment

[chdsbd]

@jay-babu What functionality would you like to see in Squawk to support your tool?

[jay-babu]

@chdsbd if i write a sql migration file like below, it should know transaction behavior is disabled:

-- atlas:txmode none

CREATE UNIQUE INDEX CONCURRENTLY IF NOT EXISTS casbin_rule_pos_register_uindex ON casbin_rule (v0, v1)
WHERE
    ptype = 'g' AND v1 = 'POS_REGISTER';

[jay-babu]

The first line tells you transaction is disabled

[jay-babu]

This is my pre-commit hook. regardless of me passing in assume-in-transaction or not, it knows that for this file that there is no transaction because of the comment above that the db migration tool uses

repos:
  - repo: https://github.com/sbdchd/squawk
    rev: v2.30.0
    hooks:
      - id: squawk
        files: migrations/.*\.sql$
        args: ["--assume-in-transaction", "--pg-version=17"]

[sbdchd]

I think it might be easiest to write a wrapper script around squawk that conditionally enables/disables the assume in transaction flag based on that comment

[jay-babu]

It would be better if I could do it per file.

…

-Jay

On Nov 12, 2025 at 7:15 PM -0500, Steve Dignam ***@***.***>, wrote: sbdchd left a comment (sbdchd/squawk#705) I think it might be easiest to write a wrapper script around squawk that conditionally enables/disables the assume in transaction flag based on that comment — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>