summaryrefslogtreecommitdiffstats
path: root/gitolite/dotfiles/.gitolite.rc (follow)
AgeCommit message (Collapse)AuthorFilesLines
2024-03-11gitolite: Force blank description for newly created repositoriesMalfurious1-0/+4
A gitolite POST_CREATE trigger is added to initialize the description file in new repos. This prevents the "Unnamed repository; edit this file ..." string from being used by default. This affects new repositories, existing projects will remain as is. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-16gitolite: Prevent repo auto-creation on clone/fetchv0.2.0Malfurious1-1/+1
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>
2023-09-15gitolite: Correct site-local code locationMalfurious1-2/+2
Per the previous commit, site-local code is now to be located directly in the git user's home directory, as static content in the docker image. Correct this setting in the RC file. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Consolidate config files into a single directoryMalfurious1-0/+206
The repository is being reworked to decouple its roles as normalmode source and gitolite-admin config. The gitolite-admin repository will be entirely separate. So there is no need to keep the conf or local directories around where they are at. Signed-off-by: Malfurious <m@lfurio.us>