GIT - 推送给(GitHub)出身的主人什么都不做 [英] GIT - pushing to (GitHub) origin master does nothing

查看:118
本文介绍了GIT - 推送给(GitHub)出身的主人什么都不做的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我分发了某人的GIT存储库:

  https://github.com/nippysaurus/toodledo-objc 

将它克隆到我的本地计算机,并显示以下信息的来源:

  *远程出处
取阅网址:https://nippysaurus@github.com/nippysaurus/toodledo-objc.git
推送网址:https ://nippysaurus@github.com/nippysaurus/toodledo-objc.git
HEAD分支:master
远程分支:
跟踪的主数
为'git pull'配置的本地分支:
主人与远程主人合并
为'git push'配置的本地参考:
主人推到主人(最新)

当我将更改推送到origin master时,git会打印所有内容都是最新的,但没有更新到我的GitHub仓库中。



这里发生了什么?

编辑:

有人建议我检查文件实际上是否有效ted ...文件已被提交,我向你保证。

  commit 0d3a21616d82c8e5a89baaf85d745fc2cfdf614f 
作者:nippysaurus< nippysaurus @ example.com>
日期:Wed Jun 1 13:19:14 2011 +1000

已更新自述

这是更新的文件:

 提交0d3a21616d82c8e5a89baaf85d745fc2cfdf614f 
作者:nippysaurus< nippysaurus @ example.com>
日期:Wed Jun 1 13:19:14 2011 +1000

已更新自述文件

diff --git a / README.mdown b / README.mdown
index fb8ee14..a71aa57 100644
--- a / README.mdown
+++ b / README.mdown
@@ -3,7 +3,7 @@ toodledo -objc

ObjectiveC中的_unofficial_ toodledo-API实现。

- 这个库目前使用[API的1.0版本](http://www.toodledo.com/info/api_doc.phpToodledo API 1.0规范),它已经是
+该库目前使用[版本1.0的API](http://www.toodledo.com/info/api_doc.phpToodledo API 1.0规范),该版本已被授予

支持:

另外,我可以看到文件的本地版本与GitHub上的版本非常不同,这些变化肯定会被添加到我的本地仓库,但不会被推送到远程仓库。

可能是如果您在另一个分支上,而不是master分支,则输入:

  git push origin HEAD:master 

所以git理解你想推高当前的HEAD而不是主分支。


I have forked someone's GIT repository:

https://github.com/nippysaurus/toodledo-objc

Cloned it to my local machine, showing the origin with the following information:

* remote origin
  Fetch URL: https://nippysaurus@github.com/nippysaurus/toodledo-objc.git
  Push  URL: https://nippysaurus@github.com/nippysaurus/toodledo-objc.git
  HEAD branch: master
  Remote branch:
    master tracked
  Local branch configured for 'git pull':
    master merges with remote master
  Local ref configured for 'git push':
    master pushes to master (up to date)

When I push my changes to "origin master" git prints "everything up to date", but nothing it updated in my GitHub repo.

What is going on here?

EDIT:

Someone is suggesting that I check thay the files were actually commited... the files were commited, I assure you.

commit 0d3a21616d82c8e5a89baaf85d745fc2cfdf614f
Author: nippysaurus <nippysaurus@example.com>
Date:   Wed Jun 1 13:19:14 2011 +1000

    updated readme

This is the file that was updated:

commit 0d3a21616d82c8e5a89baaf85d745fc2cfdf614f
Author: nippysaurus <nippysaurus@example.com>
Date:   Wed Jun 1 13:19:14 2011 +1000

    updated readme

diff --git a/README.mdown b/README.mdown
index fb8ee14..a71aa57 100644
--- a/README.mdown
+++ b/README.mdown
@@ -3,7 +3,7 @@ toodledo-objc

 An _unofficial_ toodledo-API implementation in ObjectiveC.

-This library currently uses [version 1.0 of the API](http://www.toodledo.com/info/api_doc.php "Toodledo API 1.0 spec") which has been offic
+This library currently uses [version 1.0 of the API](http://www.toodledo.com/info/api_doc.php "Toodledo API 1.0 spec") which has been offic

 Supported:

Also, I can see that the local version of the file is very different to the version on GitHub, the changes are definately being added to my local repo, but are not being pushed to the remote repo.

解决方案

It might be the case that you are on another branch than the master branch, then type:

git push origin HEAD:master

so git understands that you want to push up current HEAD and not the master branch.

这篇关于GIT - 推送给(GitHub)出身的主人什么都不做的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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