MR Approval policy blocks the MR with Secret Detection even when no secret is leaked

Summary

During a workshop with a customer on Friday, I needed to add, step by step, different policies to my group.

1. I added Secret Detection as a Pipeline Execution Policy.
2. I added an MR Approval policy for Secret Detection to require one approval
3. I tried to add other policies but all MR on my policies project were blocked due to above Approval... while no secrets were detecterd.

Steps to reproduce

Run the Security Workshop and create the policies at the Group level instead of the Project level.

Example Project

• https://gitlab.com/gitlab-learn-labs/environments/session-160096a7/iupa6d1d/my-test-group-iupa6d1d-security-policy-project/-/merge_requests/3
• https://gitlab.com/gitlab-learn-labs/environments/session-160096a7/iupa6d1d/my-test-group-iupa6d1d-security-policy-project/-/merge_requests/4

What is the current bug behavior?

• The MR Approval policy blocks the MR, requiring an approval, while no Secret is detected.

What is the expected correct behavior?

• The MR Approal policy should not require any approval.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com