我们需要添加文件，并提交已经更改/添加的文件 执行以下命令

Git添加。或者git add nameoffile #，它将添加项目中现有的文件

Git commit -m "first commit" #提交项目中的所有文件

Git push origin master

验证您没有篡改远程URL。

I just wanted to also mention that I ran into this after enabling Git as a CVS in a local Jenkins build configuration. It appears that Jenkins checked out the most recent commit of the branch I gave it and also reset my remote to correspond to the paths I gave it to the repo. Had to checkout my feature branch again and fix my origin remote url with 'git remote set-url'. Don't go pointing a build tool to your working directory or you'll have a bad time. My remote was set to a file path to my working directory, so it naturally reported everything up-to-date when I attempted to push changes with the same source and destination.

也许你想在当地开一家新分公司?

必须显式地推送一个新的本地分支:

git push origin your-new-branch-name

这是关于少年犯的一件事…你克隆一个回购，创建一个分支，提交一些更改，推送…“一切都是最新的”。我理解为什么会发生这种情况，但这种工作流程对新人非常不友好。

你是在用一个分离的脑袋工作吗?

如:

指示您的最新提交不是分支头。

警告:以下是一个git重置——很难:如果你想保存当前修改的文件，请确保首先使用git stash。

$ git log -1
# note the SHA-1 of latest commit
$ git checkout master
# reset your branch head to your previously detached commit
$ git reset --hard <commit-id>

正如git签出手册页中提到的(重点是我的):

有时能够签出不在分支顶端的提交是有用的。 最明显的例子是在标记的官方发布点检出提交，就像这样:

$ git checkout v2.6.18

Earlier versions of git did not allow this and asked you to create a temporary branch using the -b option, but starting from version 1.5.0, the above command detaches your HEAD from the current branch and directly points at the commit named by the tag (v2.6.18 in the example above). You can use all git commands while in this state. You can use git reset --hard $othercommit to further move around, for example. You can make changes and create a new commit on top of a detached HEAD. You can even create a merge by using git merge $othercommit. The state you are in while your HEAD is detached is not recorded by any branch (which is natural --- you are not on any branch). What this means is that you can discard your temporary commits and merges by switching back to an existing branch (e.g. git checkout master), and a later git prune or git gc would garbage-collect them. If you did this by mistake, you can ask the reflog for HEAD where you were, e.g. $ git log -g -2 HEAD

虽然git push表示“所有内容都是最新的”，但从技术上讲，你仍然可以推送一个分离的HEAD，正如Jonathan Benn在评论中所指出的那样

 git push origin HEAD:main

您必须指定目标分支，因为源不是分支，也没有上游目标分支。

见上面VonC的回答-我需要一个额外的步骤:

$ git log -1
- note the SHA-1 of latest commit
$ git checkout master
- reset your branch head to your previously detached commit
$ git reset --hard <commit-id>

我这么做了，但是当我尝试着去推remoterepo master时，它说 "错误:未能推动一些参考。为了防止您丢失历史记录，非快进更新被拒绝，合并远程更改(例如。'git pull')，然后再推。”

所以我做了'git拉remoterepo master'，它发现了一个冲突。我再次做了git reset——hard <commit-id>，将冲突文件复制到备份文件夹，git再次拉出remoterepo master，将冲突文件复制回我的项目，git提交，然后git推送remoterepo master，这一次它成功了。

Git不再说“一切都是最新的”，也不再抱怨“快进”。

git branch -M <desired branch>

这招对我很管用。