When we start up a new docker container with an SQL database, and want to bundle the git commits in the database, an error is then thrown.
Git synchronization failed. Git command failed with exit code 128. Errors: *** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'root@7903558b724d.(none)')
The error makes sense techinically, but since we are deploying containers (that we would like to avoid executing commands into), and are storing it inside PSUs own database / git repo - then it would be benefitial, to have these values automatically set behind the scenes.
Summary of the new feature / enhancement
When we start up a new docker container with an SQL database, and want to bundle the git commits in the database, an error is then thrown.
Git synchronization failed. Git command failed with exit code 128. Errors: *** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'root@7903558b724d.(none)')The error makes sense techinically, but since we are deploying containers (that we would like to avoid executing commands into), and are storing it inside PSUs own database / git repo - then it would be benefitial, to have these values automatically set behind the scenes.
Proposed technical implementation details (optional)
No response