Repository not set safe with persistent workspaces but container-based jobs #2271
Description
We have a setup with self-managed runners where workspaces persist over jobs. This means when second job runs checkout, it might have repository there already. It looks like there is a corner-case here that git repository is not set safe which will make git usage in that directory unreliable.
It seems the problem is that safe directory is set to container global in this context. So when running next job with fresh container the config is gone but repo remains. It is not an option to use local config since it's not possible to use local config for this override. In this case workspace uses different permission than runner due to user mismatch. (which is a problem on its own right but the entire safe directory feature is a workaround for this.