sharedRepository config option not honored

[mroi]

The git configuration option sharedRepository can be used to explicitly specify permissions of newly created files by setting it to 0xxx with the xxx part giving the permission bits in the usual octal notation.

I have a repository with sharedRepository set to 0750, and I am using the libgit2 application GitUp. But commits create new objects with world-readable permissions. I have been told by the GitUp developer, that this falls within the responsibilities of libgit2. I currently work around the problem using scripts, but it would be great if libgit2 could support sharedRepository permissions directly.

[PromyLOPh]

This still seems to be the case for v1.1.

I have the opposite problem using the libgit2-backed pygit2. It honors git’s recorded file permissions (0644 minus umask 0007) and creates files with mode 0640, even though I set sharedRepository = group. The expected mode here would be 0660. git pull/git checkout correctly honors this setting.

I assumed this setting would affect checked out files, which is not true. The setting is still not honored for files in .git though.

[ethomson]

This feels like a great place for a new contributor to jump in so I added some labels to encourage that. 😁