Purpose

• Solves the issue with random file permissions errors after release

Rationale

I found that here on PSR we had some issues writing the partial tags occasionally after PSR had created a commit. I discovered that this was because while in the Docker container, the commit action had turned certain files within the git repository (which is mounted into the container) to root owned files. Then afterword if the sha1 for the tag matched the first few characters of the sha1 of the commit then it would collide and fail with permissions errors on the .git/objects/ folder.

How did you test?

I ran this on my repository fork with a full file listing of the .git/ directory. I could see in comparison to when this project released to after this fix was implemented how the file ownership was corrected from root:root to runner:docker.

---

PR Completion Checklist

• Reviewed & followed the Contributor Guidelines

• Changes Implemented & Validation pipeline succeeds

• Commits follow the Conventional Commits standard
  and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)

• N/A Appropriate Unit tests added/updated

• N/A Appropriate End-to-End tests added/updated

• N/A Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)