I'm new to SQLFluff and am interested in a pre-commit check of changed files for rule violations. SQLFluff is working correctly, and to get it working with pre-commit I'm following the guide found here, but am confused by pre-commit asking for git credentials before doing anything.
After entering a commit message, I see:
[INFO] Initializing environment for *my gitlab URL*
Username for '*my gitlab URL*':
My org does everything through SSO so I don't have the password to give. No guide or blog post detailing the set up of pre-commit (at least that I can find) shows or says anything about credentials or configuring authentication. Running pre-commit against a file using a terminal command yields the same result. From what I understand, the provided SQLFluff hooks are client side, so I don't know why authenticating to gitlab would be necessary. I feel like I am missing something obvious, but I've done my searching and came up short. Much thanks to anybody who can tell me what I'm missing!
pre-commit autoupdate
to get that file. – Inotropic