<!-- The first four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve Gitlab currently creates a few autodeploy-tags /day in the [CNG chart repo](https://gitlab.com/gitlab-org/charts/gitlab/-/tags), which is understandable. The pull mirroring feature though always pulls tags (including these autodeploy-tags), even though some or most have no value for community contributors developing the chart. ### Intended users Developers that use the pull mirroring feature, on a project that has an upstream which (ab)uses the git repository as a metadata store for project management or other issues not directly related to code deployment. ### User experience goal An easy way to exclude or explicitly include a pattern of tags / branches / refs from pull mirroring. Protected branches is an incomplete solution, as currently tags seem to be pulled always. ### Proposal I believe the best way to fix this is to allow git ref filtering (allow / ignore) for pull mirroring, similar to how protected branches are set up. ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> Note that this is generally useful for projects that use pull mirroring, but do not want/need _all_ of the git history and structure of the upstream repository. It is further useful to decrease the amount of refs in a repository, which should increase the performance of gitlab handling that repository. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> No changes in the rights for pull mirroring. ### Documentation The following page needs updating when this feature is implemented: https://docs.gitlab.com/ee/user/project/repository/repository_mirroring.html#pulling-from-a-remote-repository-starter ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? Current users of pull mirroring <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references This is comparable to gitlab-org/gitlab#1355, but different in that we need tag filters as well.