Repository navigation
Replies: 2 comments 4 replies
|
I believe git will take the |
|
Here's what's probably biting you: Setting all four covers it: env:
- name: GIT_AUTHOR_NAME
value: "Your Name"
- name: GIT_AUTHOR_EMAIL
value: "you@example.com"
- name: GIT_COMMITTER_NAME
value: "Your Name"
- name: GIT_COMMITTER_EMAIL
value: "you@example.com"If you also want - name: GIT_CONFIG_COUNT
value: "2"
- name: GIT_CONFIG_KEY_0
value: user.name
- name: GIT_CONFIG_VALUE_0
value: "Your Name"
- name: GIT_CONFIG_KEY_1
value: user.email
- name: GIT_CONFIG_VALUE_1
value: "you@example.com"I tried both forms with git 2.43 in an empty home directory and each gave a commit with the right identity. |
Uh oh!
There was an error while loading. Please reload this page.
I am running code-server in a Kubernetes cluster, and so its entirely possible that the pods hosting it might be recreated at any point. The git config is local and, to the best of my knowledge, not stored in the code-server config. Therefore, if the pod is recreated the git config will be destroyed and I'd have to re-enter it.
Am I missing something? I couldn't find anything in the docs about how to set the Env variables to recreate these configuration items on a rebuild.
All reactions