Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

github error on create release: tag could not be created, pre-receive hooks failed

I am not by any means a sophisticated github user. I have learned the minimum handful of commands needed to add, commit, and push my project code to the public github.com repository. So far it's been working fairly well... until today when I tried to create a new release (my third).

For some reason, when I try to publish my new release, I get the message

Tag could not be created. Pre-receive hooks failed.

I have never seen this message before.

I have tried various different tag names; I have tried logging out and back in again; I have tried pre-tagging on my local disk copy of the repo; I have pushed and pulled (both ends are up to date). This about exhausts my repertoire of things to try :-(

As a relative n00b I find this message incredibly opaque (sigh). I have tried googling for it, but quickly got in over my head -- most of the hits I found were discussions about people setting up their own networked repos and installing or tweaking their own custom "pre-receive hooks", whereas I am just a dumb user of github.com apparently struggling with whatever "pre-receive hooks" they have installed (?). If anyone can at least point me in the right direction I'd be most grateful.

like image 882
De Clarke Avatar asked Oct 22 '17 23:10

De Clarke


2 Answers

Make sure you select the tag version in the dropdown. The GitHub form will let you submit when this field is blank, but it will always display the mentioned error message. (You do not need a 'v' prefix.).

The latest Github form makes this more cryptic by having a dropdown titled 'Tag:Choose or Create" that hides the fact that this field is both required but not set.

Latest Github Form GitHub Form 2

Older Github Form GitHub Form

like image 54
Steven Spungin Avatar answered Oct 10 '22 07:10

Steven Spungin


In a GitHub context, I have seen that error message in this issue

It could be a tag naming convention issue.
The GitHub release documentation recommends (enforces?) a tag following the semantic versioning naming scheme: vX.Y.Z.

As shown here, try vx.y.z.

like image 22
VonC Avatar answered Oct 10 '22 09:10

VonC