<!--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=354967) </details> <!--IssueSummary end--> Currently, the specs for a project import in https://gitlab.com/gitlab-org/gitlab/-/blob/d9a3bad64c6e2b281acdb6f5e3370ef00b705dcf/spec/services/projects/after_import_service_spec.rb#L46 iterate the `Repository::RESERVED_REFS_NAMES` to check if refs are kept. But this does not verify if all expected refs are actually in the constant. Which caused a bug in the past. The following discussion from !82326 should be addressed: - [ ] @reprazent started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82326#note_867075675): (+1 comment) > `@exit404` Thanks for tackling this. And for including the history in the description :heart:. I think this makes sense. But I do wonder if we should improve the specs to prevent this from happening again, because we [iterate](https://gitlab.com/gitlab-org/gitlab/-/blob/d9a3bad64c6e2b281acdb6f5e3370ef00b705dcf/spec/services/projects/after_import_service_spec.rb#L46) the constant that we're also testing, this why it went unnoticed before. > > `@wortschi` What do you think? I don't think this should block merging this though, this is already solving a problem.