git push

git push update/upload remote refs along with associated objects

• https://git-scm.com/docs/git-push

• Steps: git add -> git commit -> git push
• How to commit to remote branch
• Make Local Changes and Update remote Repositories

Basic commands

• git push (--help)
• git push -v
• GIT_SSH_COMMAND="ssh -v" GIT_TRACE=1 git push -vvv -u origin main
• GIT_SSH_COMMAND="ssh -v" GIT_TRACE=2 git push -vvv -u origin main
• git push -v -u origin main
• git push -v --force -u origin main
• git push -f origin master
• git push -u origin main
• git push -uf
• git push origin master
• git push -u origin master
• git push -u origin master or git push --set-upstream origin master (Used by argument-less git pull)
• git push origin HEAD:master
• git push --tags
• git push --set-upstream

Additional commands

How to skip a pipeline

• git push -o ci.skip

Examples

git push
Everything up-to-date

git push -u origin master
 
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 212 bytes | 212.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
To ssh://gitlab.yourdomain.com:2224/project/project_test.git
* [new branch]      master -> master
Branch 'master' set up to track remote branch 'master' from 'origin'.

git push xxx your-branch
To https://github.com/your-user/your-repo.git
 ! [rejected]        your-branch -> your-branch (non-fast-forward)
error: failed to push some refs to 'https://github.com/your-user/your-repo.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

git push with errors

git push -u origin master
ssh_exchange_identification: read: Operation timed out
fatal: Could not read from remote repository. 

Please make sure you have the correct access rights
and the repository exists.

[rejected]

git push
To github.com:user/proyect.git
! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'github.com:user/proyect.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

No configured push destination

git push
fatal: No configured push destination.
Either specify the URL from the command-line or configure a remote repository using

    git remote add <name> <url> 

and then push using the remote name 

    git push <name>

No upstream branch

git push
fatal: The current branch YOUR_BRANCH has no upstream branch.
To push the current branch and set the remote as upstream, use

   git push --set-upstream origin YOUR_BRANCH

error: src refspec master does not match any

• You are not allowed to force push code to a protected branch
• fatal: You are not currently on a branch
• remote: Permission to ...

Example with all steps

touch README.md
git add README.md
git commit -m "add README"
git push -u origin master

Activities

• How to commit to remote branch: git push origin

Related terms

• Make Local Changes and Update remote Repositories
• git push --follow-tags
• git config
• git push -o merge_request.create
• git merge
• git commit, git commit -an
• conan upload
• docker push
• git remote add
• git config --global --edit
• helm push
• Denied to lorks
• remote: Support for password authentication was removed on August 13, 2021.
• Remote: Repository not found.

See also

• git push [ -v | --set-upstream | -o | --set-upstream origin master | -u origin main | origin master | -u origin master | --delete master | -u | origin HEAD | --dry-run ], Git: upstream, git push --force