Skip to content

bot-token: set the git identity with env vars, not GIT_CONFIG_GLOBAL - #122

Merged
brunogbv merged 1 commit into
mainfrom
fix/121-bot-token-identity
Oct 14, 2026
Merged

brunogbv merged 1 commit into
mainfrom
fix/121-bot-token-identity

Conversation

@brunogbv

Copy link
Copy Markdown
Collaborator

GIT_CONFIG_GLOBAL captured actions/checkout's temporary global credential include, so a later submodule fetch sent Authorization twice. The action now exports GIT_AUTHOR_* and GIT_COMMITTER_* to GITHUB_ENV. mints-scoped checks a real commit; a new job checks out marola with submodules and fetches each.

Closes #121

Tested: devkit-quality.sh rc=0; actionlint on bot-token-test.yml clean; local repro of the include.path write and commit identity; live jobs run in CI only
Co-Authored-By: Claude [email protected]

GIT_CONFIG_GLOBAL captured actions/checkout's temporary global credential include, so a later submodule fetch sent Authorization twice. The action now exports GIT_AUTHOR_* and GIT_COMMITTER_* to GITHUB_ENV. mints-scoped checks a real commit; a new job checks out marola with submodules and fetches each.

Closes #121

Tested: devkit-quality.sh rc=0; actionlint on bot-token-test.yml clean; local repro of the include.path write and commit identity; live jobs run in CI only
Co-Authored-By: Claude <[email protected]>
@brunogbv
brunogbv merged commit 28f3f96 into main Oct 14, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bot-token: set the git identity with GIT_AUTHOR_*/GIT_COMMITTER_* so a submodule checkout after it does not send Authorization twice

1 participant