<!--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=426343) </details> <!--IssueSummary end--> ### Problem to solve In https://gitlab.com/gitlab-org/gitlab/-/issues/374003+ we introduced new default branch protection setting "Fully protected after initial push" which allow user with `Developer` role to perform one-time push to empty repository. The same problem can occur if when a user uses "Protected against pushes". The Developer can create a new repository but it is always empty. Enabling this feature for "Protected against pushes", will help to avoid when "Developers" of a group can create a repo but never push any code to it. <details><summary>Current State</summary>  </details> ### Proposal Add a new option for `Protected against pushes after initial push`. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->