Able to edit comments in SQL files, but the current DBDevOps pipeline fails if comments are modified after a changeset has been applied.
Comments can be added or edited in a changeset even after it has been executed.
Editing comments should not trigger changeset re-execution or checksum validation, as comments are non-functional changes.
Currently, every comment modification requires manually recalculating the checksum and rerunning the pipeline.
This behavior was validated using a test changeset where the comment was edited after the changeset had already been executed.