Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#66810 - [gitlab-shell] gitconfig should include some recommended settings

Attached to Project: Community Packages
Opened by Justin Kromlinger (hashworks) - Thursday, 28 May 2020, 16:21 GMT
Last edited by Anatol Pomozov (anatolik) - Thursday, 28 May 2020, 19:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


In gitlab-shell we already have a gitconfig file:

However, according to the GitLab docs it should include some more settings:


# Disable 'git gc --auto' because GitLab already runs 'git gc' when needed
sudo -u gitlab -H git config --global 0

# Enable packfile bitmaps
sudo -u gitlab -H git config --global repack.writeBitmaps true

# Enable push options
sudo -u gitlab -H git config --global receive.advertisePushOptions true

# Enable fsyncObjectFiles to reduce risk of repository corruption if the server crashes
sudo -u gitlab -H git config --global core.fsyncObjectFiles true

Resulting in:

name = GitLab
email = gitlab@localhost
autocrlf = input
fsyncObjectFiles = true
advertisePushOptions = true
auto = 0
writeBitmaps = true

I've tested receive.advertisePushOptions, without it you run into this:
But I'm no expert for the other options, is there a specific reason they are not included?
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Thursday, 28 May 2020, 19:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  svn rev 636633