git-push

问题 I googling a lot. but it still report an error after execute 'git push -u origin master'. Finally I execute 'git push -u origin master' success, but I really don't know where the error is. Please read on patiently the content as follow. 1, I've had a git account 'HelenZeng', now I have another account 'Snowbabe' 2, I generate two ssh key, one is id_rsa_helen, another is id_rsa_snow 3, I touch ~/.ssh/config #github.snowbabe Host github.com-Snowbabe HostName github.com User Snowbabe

问题 So here are the steps I've taken so far: Created application on openshift Cloned application's repo Deleted all files for the sample app in the cloned repo Added my project files Performed a Git-Push which completed successfully. I still see the default landing page: The only odd thing I see in the deployment logs this warning, which makes no senses because it's not my code doing that (I'm basically just trying to deploy the sample app from Express) Any ideas as to what could be causing this?

问题 I am not sure where to search from as the error list is as long as the bottom. But generally this is what I did. What I did: git clone url . git add abc.txt git commit -m "testing" git push origin master / git push Error: 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,

问题 I'm occuring a weird error running on my Windows 7 64bit system with Cygwin (latest one from their homepage) installed including ssh-agent etc. and separately the msysgit. (Cygwin terminal: git version 1.9.5.msysgit.0 ) When I try to push a git repo via Cygwin through a vpn tunnel it freezes at this position with the cursor just blinking: $ GIT_TRACE=1 git push live staging --verbose trace: built-in: git 'push' 'live' 'staging' '--verbose' trace: run_command: 'ssh' 'user@my-server.com' 'git

问题 I cloned a Repo from Perfoce into Git locally with all its history, call it SubProj , and then I pushed it to a remote repo, and used that remote repo to merge SubProj under a SuperProj . There is no way to import part of the history from Perforce to Git, either @all or none . Anyway, It went fine and I deleted the local repo, and its remote. Now, there are changes on the Perforce depot SubProj , so I cloned SubProj again with all the history, I want to push then merge with SuperProj but I do

问题 I hear that force pushing ( git push -f ) is a dangerous practice to be avoided if possible. That being said, what would be a safe procedure for doing so in the case of a private repo shared among a small team? I imagine it would be something like this: I ask team members not to push until I'm done. I fetch. I update the branch's history as needed (amend, rebase, etc.). I force push. I tell them I'm done. They do ___ to acquire and integrate the new history with their code without anything

问题 According to the git-config documentation for branch.<name>.merge : branch.<name>.merge Defines, together with branch.<name>.remote , the upstream branch for the given branch. It tells git fetch / git pull / git rebase which branch to merge and can also affect git push (see push.default ). Is there an equivalent setting to specify the upstream branch to push to, for the given branch? This is the behaviour I want to achieve - say I have a branch A with remote set to origin . On running git

问题 I committed some unnecessary code so I used: git reset HEAD~ I checked out the files and tried to push my last commits (which were correct). However, I'm receiving error: error: failed to push some refs to 'git@github.com:MyProject/MyProject.git' hint: Updates were rejected because the tip of your current branch is behind which is probably since the commit is not reverted correctly since when I do git pull, the commit is back again. How can I correctly revert this commit? additional info: git

问题 Related question: why does Git send whole repository each time push origin master The short version: When working with two Git repositories, even if 99% of the commit objects are identical, using git push to send a commit to repository B when origin is set to point to repo A causes all objects (200MB +) to be transferred. The much longer version: We have a second Git repository set up on our continuous integration server. After we have prepared our commit objects locally, instead of pushing

问题 Say you have a branch on your origin that has a ridiculously long name... $> git branch -a * master origin/master origin/branch-with-a-ridiculously-long-name And when you work on that branch locally, you want to give it a less ridiculous name, like bob . $> git checkout origin/branch-with-a-ridiculously-long-name $> git checkout -b bob $> git branch --set-upstream bob origin/branch-with-a-ridiculously-long-name When it comes time to push, what can you do such that if you run: $> git checkout