Skip to content
This repository has been archived by the owner on Sep 1, 2020. It is now read-only.

Running without an argument will destoy origin/master #78

Open
TheJosh opened this issue Dec 3, 2015 · 4 comments
Open

Running without an argument will destoy origin/master #78

TheJosh opened this issue Dec 3, 2015 · 4 comments

Comments

@TheJosh
Copy link

TheJosh commented Dec 3, 2015

Running git deploy setup without the -r and branch name clobbered existing post-receive hooks and also changed many permissions and deleted the master branch.

It should probably warn against this.

@mislav
Copy link
Owner

mislav commented Dec 3, 2015

I'm sorry that happened. I'll try to see what's going on there.

@TheJosh
Copy link
Author

TheJosh commented Dec 3, 2015

I'm guessing that but not specifying an upstream, it auto-chose "origin". Note that in our situation here, our origin server, unlike most Git hosts, is running a full version of SSH rather than a jailed shell (it's a local server and the users log in to do other tasks).

I'd imagine that it tried (and succeeded due to the full shell) at installing to "origin".

@mislav
Copy link
Owner

mislav commented Dec 4, 2015

Thanks for the explanation.

How did it destroy the master branch, though?

@TheJosh
Copy link
Author

TheJosh commented Dec 4, 2015

Not sure but a git push origin master fixed that. I also had to recreate
my post-receive hook on the server.

There appeared to be a checkout of the repository within the bare
repository (in this case it was within the /home/git/frog.git directory)
On 05/12/2015 2:24 AM, "Mislav Marohnić" [email protected] wrote:

Thanks for the explanation.

How did it destroy the master branch, though?


Reply to this email directly or view it on GitHub
#78 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants