`git push` - no output, nothing happens

Question

touch test git add test git commit -m "test" git push -u origin master 

It worked. The file has been uploaded to the repository.

 rm test cp -R ../website ./website git rm test git add website/ git commit -m "Initial" git push -u origin master 

This did not produce any results, and it seems that nothing has been done in the repository. The test file is still present in the repository.

 $ git status # On branch master # Your branch is ahead of 'origin/master' by 1 commit. # nothing to commit (working directory clean) 

---

Can anyone help?

---

Reproduction of a branch both on the client, and on the server, without any success. It works when there is only one file inside, but it just won’t push the website folder to the server.

This is the only strange thing I see; POST git-receive-pack (chunked)

Answer 1

It sounds like something related to BitBucket. Another question here had the same problem: Hanging on "POST git -receive-pack (chunked)"

The solution is to use Git + SSH, not HTTP. It seems to only affect file repositories of several megabytes.

Answer 2

This doesn't seem to be a git bug for me. If you use exactly the commands that you specified, the contents of the ../website directory ../website not be copied to the ./website directory. Try making cp -R ../website ./website to copy all the content.

Also try making git status after copying to see if the changes reflect. Try adding everything to the repository directory in the git repository by doing git add .

Let me know the results of this operation. Also, I would appreciate it if you could update the question in your directory structure.

Answer 3

Just try git push , you do not need to specify arguments, since you already used the -u option once. Also from your output, it seems that the Bitbucket server might be unavailable at this point.

Answer 4

One common reason for this is that you are entering the wrong passphrase for your SSH key. Until you clear the cached credentials, git push will never work with this remote.

The git push origin master command line will not do anything, it will slow down and not give an output.

SmartGit can "cause" this by automatically filling in the wrong password for your SSH key at the time of pressing. Clicking OK forever breaks "git push" until you go to "Settings" and clear the credentials.

Answer 5

If you use persistent SSH connections, an outdated connection problem may occur. This happened to me for the first time today after a year of using persistent SSH. Open your .ssh / config and check out ControlPath, then go there and delete the corresponding file. For me it was / tmp / git @ bitbucket.org: 22