Marking the popular workspace directories as safe for git will prevent issues running the latest versions that now check the owner of the top-level directory.
Use Cases
On kpack, and maybe other platforms, the workspace directory is owned by root and cannot easily be changed to another user. Additionally, recent stacks now include a version of git that includes a check of ownership for the top-level directory in a repository. Functionally, this has meant that builds on kpack that include a top-level .git directory and run on the latest versions of the stack could fail if they invoke any git command.
Checklist
[x] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).
Summary
Marking the popular workspace directories as safe for
gitwill prevent issues running the latest versions that now check the owner of the top-level directory.Use Cases
On
kpack, and maybe other platforms, the workspace directory is owned byrootand cannot easily be changed to another user. Additionally, recent stacks now include a version ofgitthat includes a check of ownership for the top-level directory in a repository. Functionally, this has meant that builds onkpackthat include a top-level.gitdirectory and run on the latest versions of the stack could fail if they invoke anygitcommand.Checklist