fix: configure git identity in release action before tagging#7471
Merged
DennisOSRM merged 1 commit intomasterfrom Apr 12, 2026
Merged
fix: configure git identity in release action before tagging#7471DennisOSRM merged 1 commit intomasterfrom
DennisOSRM merged 1 commit intomasterfrom
Conversation
The 'Create git tag' step was failing with 'Committer identity unknown' because git identity was only configured in the conditional 'Commit version update' step. When that step was skipped (no version changes), git identity was never set. Now git config is called directly in the 'Create git tag' step to ensure git identity is always available for annotated tag creation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Ensures the monthly release GitHub Actions workflow can always create an annotated git tag by configuring the git committer identity even when the version-bump commit step is skipped.
Changes:
- Configure
user.name/user.emailin theCreate git tagstep to prevent “Committer identity unknown” failures. - Align tag creation identity with the existing
Commit version updatebot identity.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
124
to
128
| - name: Create git tag | ||
| run: | | ||
| git config user.name "github-actions[bot]" | ||
| git config user.email "github-actions[bot]@users.noreply.github.com" | ||
| git tag -a "${{ steps.version.outputs.tag }}" -m "Release ${{ steps.version.outputs.version }}" |
There was a problem hiding this comment.
The git identity config is now duplicated between the conditional "Commit version update" step and this always-run tag step. Consider moving the config into a dedicated always-run step (or making the scope explicit with --local) so there’s a single place to keep user.name/user.email consistent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The release action was failing with:
Root Cause
The 'Create git tag' step requires git identity to be configured, but the identity config only happens in the conditional 'Commit version update' step. When that step is skipped (e.g., when version is unchanged), git identity is never set.
Solution
Configure git identity directly in the 'Create git tag' step before creating the annotated tag. This ensures git identity is always available regardless of whether the commit step runs.
Changes
git config user.nameandgit config user.emailto 'Create git tag' stepgithub-actions[bot]identity (consistent with commit step)Fixes the failure in the monthly release workflow.