alembic-ini-db-url-triggers-secret-scanner-on-commit

Placing a database URL directly in alembic.ini causes the pre-commit secret scanner to block the commit. The fix is to leave the URL field empty in alembic.ini and rely entirely on the RSAME_DATABASE_URL (or equivalent) environment variable, which alembic env.py already reads. This pattern should be applied to all new projects using Alembic from the start.

Related

• alembic-ini-dev-db-url-triggers-secret-scanner
• alembic-ini-db-url-blocks-commit-use-env-var
• alembic-ini-hardcoded-url-triggers-secret-scanner
• alembic-ini-must-have-empty-db-url-use-env-var
• git-secret-scanner-blocks-alembic-ini-db-url
• test-credential-literals-flagged-by-secret-scanner
• alembic-ini-db-url-triggers-secret-scanner
• r-dash-postgres-creds-mismatch-pre-existing-not-wave3-regres
• r-dash-echarts-pnpm-install-required-after-wave3
• makefile-awk-help-extractor-excludes-digit-containing-target
• dependabot-limit-zero-blocks-bumps-not-security