<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Today, when creating or modifying a push rule at the instance level or at the group level, the rule will apply to any new project created within the instance or the group. However, this does not apply to existing projects. Users need to go to the projects settings one by one to apply the same push rule: https://docs.gitlab.com/user/project/repository/push_rules/#override-global-push-rules-per-project This issue proposes that the instance or group setting should apply automatically to all projects, both new and existing. This would ensure that a standard is applied by default and reduce manual processes. The settings should give the option to only apply the rule to newly created projects. <!-- 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. --> <!-- 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/ -->