<!-- 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. --> [Project templates](https://docs.gitlab.com/ee/user/group/custom_project_templates.html) are a great feature that we recently started using, and it occurred to me that if we are using templates, we might also want to enforce that changes in the templates are also applied in projects created from the template. For example, we use git pre-commit hooks to run certain checks on our commits locally before we push, and the pre-commit hooks would usually be included in our template because we want all of our projects to have a basic set of hooks configured when they are created. These hooks are versioned upstream and so when there is an update, we currently have to update each project that is using these hooks one-by-one, which is cumbersome with several dozen projects, and I couldn't imagine keeping them all in sync as our needs grow into the hundreds, and that's in addition to updating the project templates so that new projects get the updated version. We would like to request the ability to keep projects in sync with their upstream templates. <!-- 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: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->