Need a mechanism or process to handle UI-based commits
When the secrets are introduced by the GitLab UI, rather than a git push
, there's no way to bypass the check and merge anyway. This is an annoyance in the case of trying to quickly edit files online, but more problematic when it comes to MRs across forks.
In order to do this, the maintainers need to fall back to the command line, add the fork in as a remote, then manually execute the merge, reviewing the secrets at the same time. If any more changes are made, this needs to be repeated. It would be better if there was a way to mark particular incoming commits as safe from secrets without resorting to the manual effort. I have no idea what that would be.