Follow-up from "Clear merge request error on push to source branch"
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=217822)
</details>
<!--IssueSummary end-->
The following discussion from !32001 should be addressed:
- [ ] @stanhu started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/32001#note_342120774):
> The existing `@merge_request` has `master` as the source branch and `feature` as the target branch, which ends up being an empty diff. We should probably revisit that change as it's not representative of a "real" merge request, and so the `does not clear merge errors` test case would not be handled properly.
>
> I think we should refactor this test to use `let_it_be` and use this source branch, but I'll save that for another merge request.
issue