Secrets: never commit them, detect them with Gitleaks and clean the history

Objective

Understand why a secret that enters Git must be considered compromised, know how to detect it automatically with Gitleaks (on your workstation, in a Git hook and in CI), and apply the right procedure after a leak: revoke and replace first, purge the history afterwards.