Possible clone bug?

During the clone phase I am getting this issue, I am pretty sure this is caused by a force push to a commit, ie if you amend a commit and push it up to git seems this should be handled or is there some other issue that maybe causing this ?

This is from an installation integrated with github.

First, rewinding head to replay your work on top of it...
fatal: empty ident name (for <>) not allowed

Also another issue I have noticed is with pull requests, they show in the drone web interface like this.

opened pull request #2 to master 

The issue being all pull requests are called #2 should I open these on github I know the current code base is not public currently ?

this was fixed last week in the latest drone/git image. You likely have a stale version of the image in your local docker cache.

okay cheers I will clear things out and try again is that both issues resolved ? the incorrect build number and the git ident issue ?

@bradrydzewski Looks the the ARM and ARM64 images in Drone Cloud haven’t been updated; seeing this exact issue.