As per my response to onefetch - can you please instead use the names etc-gitconfig and gitconfig for these interfaces to keep consistency with other snaps?
Also can you please provide some details on why this access is needed for hugo? Thanks.
As per my response to onefetch - can you please instead use the names etc-gitconfig and gitconfig for these interfaces to keep consistency with other snaps?
Yes, for sure! Sorry for the oversight. I have just pushed the fix to gohugoio/hugo master in commit fd3953c:
Also can you please provide some details on why this access is needed for hugo ? Thanks.
Can the gitinfo problem be fixed by adding a gitconfig to the snap package and using layout: to map it to /etc/gitconfig to alleviate the requirement to access the host gitconfig? That would get this particular feature working quicker than waiting for the vote.
It might but then it won’t be able to access the real git config and so may not respect the users configured name etc - better to just do the right thing here and provide access via system/personal-files.
+1 from me for auto-connect of system-files named etc-gitconfig for read access to /etc/gitconfig and for personal-files named gitconfig for read access to ~/.gitconfig and ~/.config/git/config for hugo as this is a standard feature for hugo projects to be able to access and include this information.
+2 votes for, 0 votes against, granting auto-connect and use of system-files named etc-gitconfig for read access to /etc/gitconfig and for personal-files named gitconfig for read access to ~/.gitconfig and ~/.config/git/config for hugo. This is now live.