推到一个git存储库不起作用 [英] pushing to a git repository does not work

查看:136
本文介绍了推到一个git存储库不起作用的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚刚开始使用GIT(我是来自CVS),并希望使用Git设置类似于cvs / svn的东西。我执行了以下步骤:

  cd o:/ repository 
git init

cd <工作目录>
git clone o:/ repository

我现在创建了一个名为file.txt的文件, b














> git add file.txt
git commit file.txt

这两个似乎都很好。



当我做
git push 时,出现以下错误:

 没有共同的引用和没有指定;什么也不做。 
也许你应该指定一个分支,比如'master'。
fatal:远程端意外挂起
错误:未能将某些文件推送到'o:/ repository'

我试着先做一个pull,并且指定了push命令的起源和主变体,但没有任何工作。

有人可以请告诉我我错过了什么。我正在运行Windows 7 64位。



我也试过

  git push origin master 

,我得到以下结果:

 计数对象:3,完成。 
写入对象:100%(3/3),251字节,完成。
合计3(delta 0),重用0(delta 0)
开箱对象:100%(3/3),完成。
remote:error:拒绝更新签出分支:refs / heads / master
remote:error:默认情况下,更新非裸仓库中的当前分支
remote:error:is否则,因为它会使索引和工作树不一致
remote:error:用你推送的内容,并且需要'git reset --hard'来匹配
remote:error:工作树到HEAD 。
remote:错误:
remote:错误:您可以在远程存储库中将'receive.denyCurrentBranch'配置变量设置为
remote:error:'ignore'或'warn',以允许推入
remote:错误:当前分支;然而,除非你
remote:error:安排它更新它的工作树来匹配你在
remote:error:other方面推送的内容,否则不建议这样做。
remote:error:
remote:error:为了压制此消息并保持默认行为,请将
remote:error:'receive.denyCurrentBranch'配置变量设置为'拒绝'。
到O:/ repository
! [remote rejected] master - > master(分支目前被检出)
错误:未能将一些文件推送到'O:/ repository'


这发生在几周前的我们身上。这意味着你有一个工作目录在你的源代码仓库签出,你不能推送覆盖。



在你需要裸机的仓库。我不知道用一个命令来做这件事的方法。我所做的(在原始资料库)

 > mv repository repository.old 
> git clone --bare repository.old repository

我看到你的情况的起源是o: /存储库。来源不应该是签出的工作副本,因此您可以按照上面的说明初始化存储库或复制副本。为了得到你描述过的场景:

  cd o:/ repository 
git init --bare

cd<工作目录>
git clone o:/ repository

git push origin master

这应该适用于你:



良好的阅读: http://www.gitready.com/advanced/2009/02/01/push-to-only-bare-repositories.html


I am just starting out with GIT (i'm coming from cvs) and would like to set up something akin to cvs/svn with Git. I performed the following steps:

cd o:/repository
git init

cd <working directory>
git clone o:/repository

i now created a file called file.txt with some content doing a "git status" lists appropriate changes.

I then do

git add file.txt
git commit file.txt

and both seem to work fine.

When i do git push, i get the following error:

No refs in common and none specified; doing nothing.
Perhaps you should specify a branch such as 'master'.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to 'o:/repository'

I tried doing a pull first, as well as specifying origin and master variations to the push command but none work.

Can someone please tell me what i am missing. I am running Windows 7 64 bit.

Ps. I also tried

git push origin master

and i get the following:

Counting objects: 3, done.
Writing objects: 100% (3/3), 251 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
remote: error: refusing to update checked out branch: refs/heads/master
remote: error: By default, updating the current branch in a non-bare repository
remote: error: is denied, because it will make the index and work tree inconsistent
remote: error: with what you pushed, and will require 'git reset --hard' to match
remote: error: the work tree to HEAD.
remote: error:
remote: error: You can set 'receive.denyCurrentBranch' configuration variable to
remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into
remote: error: its current branch; however, this is not recommended unless you
remote: error: arranged to update its work tree to match what you pushed in some
remote: error: other way.
remote: error:
remote: error: To squelch this message and still keep the default behaviour, set
remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.
To O:/repository
 ! [remote rejected] master -> master (branch is currently checked out)
error: failed to push some refs to 'O:/repository'

解决方案

This happened to us a few weeks ago. It means that you have a working directory checked out in your origin repository and you cannot push to overwrite.

at the origin you need to bare the repository. I don't know of a way to do it with one command. What I did (at the origin repository)

> mv repository repository.old
> git clone --bare repository.old repository

I see that the origin in your case is the o:/repository. The origin, should not be a checked out working copy, so you can init a bare repository or copy as per above. To get the scenario you described to pass:

cd o:/repository
git init  --bare

cd <working directory>
git clone o:/repository

git push origin master

this should work just fine for you:

good reading: http://www.gitready.com/advanced/2009/02/01/push-to-only-bare-repositories.html

这篇关于推到一个git存储库不起作用的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆