Unset GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL in Codespaces workspace (2022-06)

[tnir]

Original post: Jun 18, 1:33 PM

I would like GitHub to unset GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL in a Codespaces’ workspace.

I always need to unset these environment variables in a new Codespaces’ workspace.

$ env | grep ^GIT_C
GIT_COMMITTER_NAME=GitHub
GIT_COMMITTER_EMAIL=noreply@github.com

If you try to unset them by yourself, you will run into a problem as described below:

cf. Failed to create a Codespace

[tnir]

Today I found the problem is resolved now... Anyone knows?

$ env | grep ^GIT_C | wc -l
0

[douglascamata]

I rebuilt my container in an already existing Codespace and the env vars are still there.

Also created a new Codespace and they were there still.

[douglascamata]

@tnir I don't think this is globally solved yet. Can you try out creating a new Codespace in a random repo that doesn't have devcontainer steps to unset those vars? i.e. I just tested in https://github.com/parca-dev/parca-agent and the env vars were present.

[tnir]

@douglascamata I tested the repo you showed above, and it works to me. GitHub might be rolling out this improvement by user. I hope you get this bugfix soon! (As 2 day passed, you might already got it)

[bam80]

I still see these vars in my workspace, has the problem returned?
https://github.com/orgs/community/discussions/20599#discussioncomment-10783057

[bam80]

devcontainer steps to unset those vars?

@douglascamata could you elaborate which are those?