Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pre-receive fails due to empty oldrev #49

Open
2twong opened this issue Nov 19, 2015 · 5 comments
Open

pre-receive fails due to empty oldrev #49

2twong opened this issue Nov 19, 2015 · 5 comments

Comments

@2twong
Copy link

2twong commented Nov 19, 2015

oldrev is empty at line 54 which causes git diff on line 57 of pre-receive to fail.

If I checkout master to a new branch, and push the new branch to origin/newbranchname, oldrev == 0{40} in pre-receive, newrev gets set to master, but oldrev gets set to empty and so the git diff on line 57 fails, due to the grep -v master

Reproducer with excerpt from pre-receive with set -x:

$ git branch
* master
$ git checkout -b p/newname
$ git push origin p/newname
..
remote: + oldrev=
remote: ++ git diff --name-only master --diff-filter=ACM
remote: fatal: This operation must be run in a work tree 
..

You can see oldrev is empty because of line 54:

oldrev=`git show-branch | grep -v '\*' | grep -v "master"...`
@drwahl
Copy link
Owner

drwahl commented Nov 19, 2015

Ya, this has been a long time bug. It only happens (as far as I know) on new branch pushes. I've gotten around it in the past by just disabling the server-side hook when pushing new branches, though I understand that is a horrible work around.

If someone can come up with a way to solve this, I'd love a PR!

@2twong
Copy link
Author

2twong commented Nov 19, 2015

Is there a part of the hook that can be disabled for the case of a new branch push?

@drwahl
Copy link
Owner

drwahl commented Nov 19, 2015

Actually, looks like I may be off base here. d0a01ba addressed the issues I was referring to. I'll need to dig deeper into this to see what is going on...

@2twong
Copy link
Author

2twong commented Nov 20, 2015

Thanks drwahl

@jcpunk
Copy link

jcpunk commented Mar 23, 2016

#71 should fix the issue

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

No branches or pull requests

3 participants