<!--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=34436) </details> <!--IssueSummary end--> From https://gitlab.com/gitlab-org/gitlab/issues/34310, there was a fork of `www-gitlab-com` that had a lot of loose refs. It failed to pull because the loose ref `gerir/infra/kpi` conflicted with the new ref `gerir/infra/kpi/targets`. I'm wondering if we have a general problem where we're calling `git pack-refs` without the `--all` flag. This might explain why we are seeing more loose refs than we would expect. It could just be a pull mirror issue. If we aren't able to run `update-refs` because of a conflict branch name where `a/b` exists already but `a/b/c` is created, we may want to pack refs.