Merge trains being blocked by Secret Push Protection
Overview
We've had a number of internal reports that merge trains are being blocked by Secret Push Protection - Slack thread (internal only). We're still investigating the impact, but at first glance this seems to be affecting MRs that are quite a bit behind master.
The issues started when this recent feature enhancement was deployed to Production.
Examples
Workarounds
If you have started a merge train and it fails with Something went wrong during merge pre-receive hook. PUSH BLOCKED: Secrets detected in code changes..., the quickest fix will be to add [skip secret push protection] to the merge commit body. Example for reference
Adding [skip secret push protection] to the commit body may also helpful in getting past the error before it is merged.
Another possible workaround is to run /rebase on the MR.