summaryrefslogtreecommitdiffstats
path: root/gitolite
diff options
context:
space:
mode:
authorMalfurious <m@lfurio.us>2023-09-16 14:56:41 -0400
committerMalfurious <m@lfurio.us>2023-09-16 14:56:41 -0400
commit5f5cab13b85c6ca5948581692c7be4c994908703 (patch)
tree09ee86b45e1fabea36d2b2bb7115ba0791d69df2 /gitolite
parentfcf7dc53547554507ed0fe76acd78d1ac0456d9e (diff)
downloadsrcnode-5f5cab13b85c6ca5948581692c7be4c994908703.tar.gz
srcnode-5f5cab13b85c6ca5948581692c7be4c994908703.zip
gitolite: Prevent repo auto-creation on clone/fetchv0.2.0
I'm considering this default behavior as a bug for normalmode. The creation of a repository via a read activity seems far too accidental for my taste. Repositories are created by pushing to them. This does mean that: git clone <new-url> ... git push is no longer a shorthand for: git init git remote add origin <new-url> ... git push I'm ok with that. Signed-off-by: Malfurious <m@lfurio.us>
Diffstat (limited to 'gitolite')
-rw-r--r--gitolite/dotfiles/.gitolite.rc2
1 files changed, 1 insertions, 1 deletions
diff --git a/gitolite/dotfiles/.gitolite.rc b/gitolite/dotfiles/.gitolite.rc
index eefc022..bd661de 100644
--- a/gitolite/dotfiles/.gitolite.rc
+++ b/gitolite/dotfiles/.gitolite.rc
@@ -128,7 +128,7 @@
# user-visible behaviour
# prevent wild repos auto-create on fetch/clone
- # 'no-create-on-read',
+ 'no-create-on-read',
# no auto-create at all (don't forget to enable the 'create' command!)
# 'no-auto-create',