You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The v1.6.0 release of this action has broken for us with an error about user config. We've pinned to v1.5.1 for the time being as a workaround. It's a private repo, but happy to share any other details that would be useful.
We're using self-hosted runners for our pipeline - not sure if that's relevant but the auto-detected email address ('runner@ks-1cpu-1gi-v56-bxd79-bh2nj.(none)) is the user and name of the pod running the job.
Run EndBug/latest-tag@v1.5.1
with:
ref: 2.1.5601.2377
description: 2.1.5601.2377
force-branch: false
Setting up git user...
Using '2.1.5601.2377' as tag name.
Creating annotated tag...
Pushing updated tag to repo...
To https://github.com/glean-notes/glean
* [new tag] 2.1.5601.2377 -> 2.1.5601.2377
v1.6.0 output (not working):
Run EndBug/latest-tag@latest
with:
ref: 2.1.5601.1720
description: 2.1.5601.1720
force-branch: false
git-directory: /runner/_work/glean/glean
Running git commands within /runner/_work/glean/glean
Using '2.1.5601.1720' as tag name.
Setting up git user...
Creating annotated tag...
Error: Command failed: git -C /runner/_work/glean/glean tag -a -f -m "2.1.5601.1720" 2.1.5601.1720
Committer identity unknown
*** Please tell me who you are.
Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: unable to auto-detect email address (got 'runner@ks-1cpu-1gi-v56-bxd79-bh2nj.(none)')
The text was updated successfully, but these errors were encountered:
Hi, thanks for reporting this
I actually encountered this as well the first time i tested the action (on GitHub-hosted runners!), but wasn't able to reproduce it :/
I'm going to release a patch that adds some debug logs, since as of now there's much debug info to work with. I'm gonna get back to you soon with this ✌🏻
The v1.6.0 release of this action has broken for us with an error about user config. We've pinned to v1.5.1 for the time being as a workaround. It's a private repo, but happy to share any other details that would be useful.
We're using self-hosted runners for our pipeline - not sure if that's relevant but the auto-detected email address (
'runner@ks-1cpu-1gi-v56-bxd79-bh2nj.(none)
) is the user and name of the pod running the job.Our config is:
v1.5.1 output (working):
v1.6.0 output (not working):
The text was updated successfully, but these errors were encountered: