Running into that "safe.directory" warning is super common with recent Git updates. It's Git being extra cautious about your repo's ownership or permissions.
Here's the quick fix:
The Go-To Solution
Open your terminal or Git Bash inside your repository's root folder and run this command:

git config --global --add safe.directory "%(prefix)///FULL/PATH/TO/YOUR/REPO"

Just replace FULL/PATH/TO/YOUR/REPO with the actual, absolute path to your project. This tells Git to trust that specific directory.
Alternative (Use Carefully)
If you're absolutely sure about your setup and want to trust all directories, you can use:

git config --global --add safe.directory "*"

Be cautious with this one, especially on shared systems, as it broadens the security scope.
Once you run either command, try pushing again. The warning should be gone!

This function should not exist in git code base. If the repo is on a physical or UNC path, then it should not matter which user owns what as long as the directories are writable. It's none of git's business which user owns .git because it is on the user's owned system and usually on the user's private property, therefore the user's own. Git is not part of decision making as to which user account owns which path.
I am wasting my breath on this because the above solution is not applicable in 100% cases and we should not even begin to worry about satisfying this absurd requirement: for the owner of a sub-path to be the same as other sub-paths. Variances are possible due to network share or NTFS folder mounting.