Honor the repository permssions set with the umask or
core.sharedRepository when creating directories by using tools.MkdirAll.
Pass an appropriate configuration or filesystem object through as needed
to ensure that we can query the proper permissions. Add a test that
these code paths work by cloning a new repository and then performing
some operations on it.
Note that in the test, we match patterns with either the setgid bit
clear or set, since it may be set or not depending on whether the system
has SysV or BSD group semantics.
In order to manage a shared repository easily among multiple users, Git
has the core.sharedRepository variable, which is used to set permissions
for writing objects and files in the repository. Teach Git LFS to
handle this as well by teaching the existing temporary file code to
honor this setting over the umask. Since this logic is complex, add
unit and integration tests to ensure that all the code paths are
covered.
When writing files to the LFS file storage, we create a temporary file
and rename it into its correct place. Use the function that was
recently introduced to create a temporary file that honors the umask.
This should make all uses of Git LFS honor the umask, since Git handles
writing the working tree files for us.
We compute the proper permissions value on demand. In a future commit,
we'll need to read the configuration file, and on clone, we'll want to
wait to read the configuration until we have a repository.
Add a test for this and skip it on Windows, since we cannot be
guaranteed to have POSIX permission support there.
