Updating label for whitelist deploy keys force push

notes.txt

@@ -0,0 +1,28 @@
+NOTES:
+
+- The logic behind the box disabling/enabling is the class `toggle-target-enabled` with `data-target=#target-id`
+
+
+TODO:
+- In PR update UI, currently you can Update by merge
+  - We need to keep this, but also allow Update by Rebase iff CanForcePush
+
+
+- Ensure logic is correct for saving
+    - Saving the whitelist users/teams correctly DONE
+
+- Check rules is consistent DONE
+- Apply backend logic (look at how normal pushing is done currently)
+
+- Make sure format looks like on new rule creation DONE
+
+- Force push ALSO requires normal push DONE
+    - Make it so option is disabled if regular push is also disabled
+
+
+- Check if API is updated at all (might need to update documentation)
+
+- Localise strings in template DONE for Eng
+
+repo.settings.protect_enable_force_push
+repo.settings.protect_enable_force_push_desc

options/locale/locale_en-US.ini

@@ -2298,7 +2298,7 @@ settings.protect_whitelist_teams = Whitelisted teams for pushing:
 settings.protect_whitelist_search_teams = Search teams…
 settings.protect_force_push_whitelist_users = Whitelisted users for force pushing:
 settings.protect_force_push_whitelist_teams = Whitelisted teams for force pushing:
-settings.protect_force_push_whitelist_deploy_keys = Whitelist deploy keys with write access to push.
+settings.protect_force_push_whitelist_deploy_keys = Whitelist deploy keys with write access to force push.
 settings.protect_merge_whitelist_committers = Enable Merge Whitelist
 settings.protect_merge_whitelist_committers_desc = Allow only whitelisted users or teams to merge pull requests into this branch.
 settings.protect_merge_whitelist_users = Whitelisted users for merging: