(allura) 02/06: Added scm.force_push.git.enabled flag

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

asf-gitbox-commits pushed a commit to branch dc/686
in repository https://gitbox.apache.org/repos/asf/allura.git

commit cdda319c09593eb1f1f1a22e54bb4f57fe611428
Author: Daniel Castillo <da...@slashdotmedia.com>
AuthorDate: Fri Aug 7 20:10:47 2026 +0000

    Added scm.force_push.git.enabled flag
---
 Allura/development.ini | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/Allura/development.ini b/Allura/development.ini
index 347c87480..60d349c8a 100644
--- a/Allura/development.ini
+++ b/Allura/development.ini
@@ -466,12 +466,8 @@ repo_refs_cache_threshold = .01
 scm.commit.git.detect_copies = true
 scm.commit.hg.detect_copies = false
 
-; Let repo admins enable/disable force push on their own git repos.  Only turn this on if
-; your git host honors receive.denyNonFastForwards in each repo's own config file; Allura
-; writes that value and nothing else.  When off, Allura never touches any repo's config.
-; Note that turning this off does not revert repos that were already toggled on: they keep
-; receive.denyNonFastForwards = false on disk, with the admin UI hidden so nobody can see or
-; change it.  Revert any enabled repos before disabling this setting.
+; Let repo admins toggle force push on their own git repos; only enable if your git host
+; honors receive.denyNonFastForwards.  Turning it off does not revert repos already enabled.
 ;scm.force_push.git.enabled = true
 
 ; One-click merge is enabled by default, but can be turned off on for each type of repo