Skip to content

Fix catalog proposal commit failing in CI (no git identity) - #18

Merged
dbose merged 2 commits into
mainfrom
fix-catalog-commit-identity
Sep 12, 2026
Merged

dbose merged 2 commits into
mainfrom
fix-catalog-commit-identity

Conversation

@dbose

@dbose dbose commented Sep 12, 2026 •

Copy link
Copy Markdown
Owner

No description provided.

dbose and others added 2 commits September 12, 2026 17:28
checkout_branch produces a fresh clone with no local git identity, and its
docstring promises the checkout is "ready to propose from". On a host without a
global git config (CI runners, containers) a commit into it fails with exit 128
("empty ident name") — which is why test_a_proposal_pushes_back_to_the_models_own_repo
failed in GitHub Actions but passed on developer machines that have a global
identity.

Set a local user.name/user.email on the checkout (the same identity publish()
already commits under), so a commit into a materialised proposal branch works
regardless of the host's global git config. Pre-existing latent bug, surfaced by
a CI run; unrelated to the docs/MCP changes.

Verified by reproducing the CI environment locally (GIT_CONFIG_GLOBAL=/dev/null,
no GIT_AUTHOR_* set): the catalog suite fails before the fix and passes after.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dbose
dbose merged commit 63a2c23 into main Sep 12, 2026
2 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.

1 participant