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
{{ message }}
This repository has been archived by the owner on Sep 1, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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".
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: