Skip to content

fix(release): set git identity before gitPublishCommit#24

Merged
musketyr merged 1 commit into
masterfrom
fix/release-git-identity
May 22, 2026
Merged

fix(release): set git identity before gitPublishCommit#24
musketyr merged 1 commit into
masterfrom
fix/release-git-identity

Conversation

@musketyr
Copy link
Copy Markdown
Collaborator

Summary

After PR #23 cleared the asciidoctor failure, the next 1.0.0.RC1 / 1.0.0.RC2 release attempt fails on :guide:gitPublishCommit because the runner has no git user identity set:

git config --global user.email "you@example.com"
git config --global user.name "Your Name"

This PR adds a Configure git identity for gitPublishCommit step that pins the identity to Agorapulse Bot / oss@agorapulse.com just before the ./gradlew gitPublishPush ... invocation. Matches the pattern that was landed on micronaut-rethrow when the same workflow change hit Gradle 9.

Test plan

  • Once merged, re-cut the release (recreate the GitHub Release for the existing 1.0.0.RC2 tag, or tag 1.0.0.RC3) so the publishing workflow can run end-to-end

🤖 Generated with Claude Code

The 1.0.0.RC1 retry now reaches `:guide:gitPublishCommit` and crashes
because the runner has no git user identity set, so the commit step
prints the standard `git config --global user.email "you@example.com"`
hint and exits 1.

Add a setup step that pins the identity to the agorapulse-bot
("Agorapulse Bot" / oss@agorapulse.com) just before the `./gradlew
gitPublishPush ...` invocation. Matches the pattern that landed on
micronaut-rethrow when the same workflow change hit Gradle 9.
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