<!--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=457680) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Gitlab makes it easy to mirror a repo to a remote location. It pushes: - all branches or only protected branches (choosable) - all tags (not choosable) When pushing protected branches only, we may want to not push tags pointing non-protected branches content. Such feature can be seen as privacy helpful. Another way to achieve the same result may be a choice about tag mirroring (all/annotated only/none) since one can carefully create lightweight tags when he/she doesn't want it to be mirrored but this would be more error prone and unfriendly for large histories. At the end, choices about tags to mirror would be great among (all/all-annotated/reachable/reachable-annotated/none) in my opinion. As a matter of context, I reached this issue on a repository with split history, trying to push-mirror only the new main branch and not the disconnected legacy master branch. <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->