git push to existing remote branch
To do this you use a refspec, as explained in the git push documentation. For example: git push origin local_branch_name:remote_branch_name
git-push
git push NOT current branch to remote
All those “another another” in the original question, the answer and lots of comments are so confusing (which is a perfect example of why it is important to name your things right in the first place), I can’t help helping (pun not intended) to write yet another answer as below. Q: Is there a way … Read more
When should I use “git push –force-if-includes”
TL;DR The new-in-Git-2.30 –force-if-includes does nothing unless you also include –force-with-lease. If you do use –force-with-lease, that alone can suffice. I’m not convinced of the utility of –force-if-includes myself and would personally use a multi-step process: git fetch <remote> # get commit(s) from remote git show <remote>/<name> # inspect their most recent commit # to … Read more
Git push failing HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
Increase the Git buffer size to the largest individual file size of your repo: git config –global http.postBuffer 157286400
Pushing code from one branch of a repo to another branch of another repo
Yes, you can push any local branch to any remote branch. The syntax is git push <remote name, e.g. origin> <local branch name>:<remote branch name> If your current branch (the one you want to push) is called develop, the command would be git push ME develop:x
Logon failed, use Ctrl + C to cancel basic credential prompt
Fitz_Hoo is right! I just wanted to give a more detailed explanation that fix my issue. Essentially GitHub deprecated their password authentication recently (you can read more by clicking here). Now instead of adding your username/email and password, you will login with your browser. The image below is the new interface. As Fitz_hoo mentions, you … Read more
Why is `git push –force-with-lease` failing with “rejected … stale info” even when my local repo is up to date with remote?
In my case a plain git fetch followed by the push again solved the problem.
Git prevents pushing after amending a commit
This should only be the case if you’re amending an already-pushed commit. Generally you should never do that as you’re then modifying published history. In your case however, you should be able to get away with push -f, which will overwrite the remote commit with your amended revision.
GitHub – error: failed to push some refs to ‘git@github.com:myrepo.git’
Your origin repository is ahead of your local repository. You’ll need to pull down changes from the origin repository as follows before you can push. This can be executed between your commit and push. git pull origin development development refers to the branch you want to pull from. If you want to pull from master … Read more
git@github.com: Permission denied (publickey)
You’re accessing GitHub through SSH. First generate an SSH key pair; then add the public key to GitHub. Generate key pair, github prefers the “Ed25519 algorithm” ssh-keygen -t ed25519 -C “your_email@example.com” It still allows using rsa for systems that don’t support Ed25519 ssh-keygen -t rsa -b 4096 -C “youremail@example.com” See more at https://help.github.com/en/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent and https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account