From 18449ad2eb6ac828d8e3401bbd0ae268508ae47d Mon Sep 17 00:00:00 2001
From: John Gaughan <jgaughan@gitlab.com>
Date: Thu, 1 Feb 2024 06:01:12 +0000
Subject: [PATCH] Remove misleading step from "Allow force push" instructions

---
 doc/user/project/protected_branches.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/doc/user/project/protected_branches.md b/doc/user/project/protected_branches.md
index 131dc1041aae7..29a6809d1d603 100644
--- a/doc/user/project/protected_branches.md
+++ b/doc/user/project/protected_branches.md
@@ -287,8 +287,6 @@ To protect a new branch and enable force push:
 1. From the **Branch** dropdown list, select the branch you want to protect.
 1. From the **Allowed to push and merge** and **Allowed to merge** lists, select the settings you want.
 1. To allow all users with push access to force push, turn on the **Allowed to force push** toggle.
-1. To reject code pushes that change files listed in the `CODEOWNERS` file, turn on the
-   **Require approval from code owners** toggle.
 1. Select **Protect**.
 
 To enable force pushes on branches that are already protected:
-- 
GitLab