| title | intro | redirect_from | versions | shortTitle | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Pushing commits to a remote repository |
Use `git push` to push commits made on your local branch to a remote repository. |
|
|
Push commits to a remote |
The git push command takes two arguments:
- A remote name, for example,
origin - A branch name, for example,
main
For example:
git push REMOTE-NAME BRANCH-NAMEAs an example, you usually run git push origin main to push your local changes
to your online repository.
To rename a branch, you'd use the same git push command, but you would add
one more argument: the name of the new branch. For example:
git push REMOTE-NAME LOCAL-BRANCH-NAME:REMOTE-BRANCH-NAMEThis pushes the LOCAL-BRANCH-NAME to your REMOTE-NAME, but it is renamed to REMOTE-BRANCH-NAME.
If your local copy of a repository is out of sync with, or "behind," the upstream
repository you're pushing to, you'll get a message saying non-fast-forward updates were rejected.
This means that you must retrieve, or "fetch," the upstream changes, before
you are able to push your local changes.
For more information on this error, see AUTOTITLE.
{% ifversion secret-scanning-push-protection-for-users %}
To maintain the security of the repository you're pushing to, {% data variables.product.github %}'s push protection automatically protects you from accidentally committing secrets to public repositories on {% data variables.product.prodname_dotcom_the_website %}. Exposed secrets can pose serious security risks to your repository and your supply chain. If {% data variables.product.github %} detects that the commit you're attempting to push contains a supported secret, it blocks the push. In order to resolve the block, you should either:
- Remove the secret from your commit(s). For more information, see Resolving a blocked push.
- Follow the provided URL to see options to allow the push. For more information, see Bypassing push protection
To learn more about push protection, see AUTOTITLE.
{% endif %}
By default, and without additional parameters, git push sends all matching branches
that have the same names as remote branches.
To push a single tag, you can issue the same command as pushing a branch:
git push REMOTE-NAME TAG-NAMETo push all your tags, you can type the command:
git push REMOTE-NAME --tagsThe syntax to delete a branch is a bit arcane at first glance:
git push REMOTE-NAME :BRANCH-NAMENote that there is a space before the colon. The command resembles the same steps
you'd take to rename a branch. However, here, you're telling Git to push nothing
into BRANCH-NAME on REMOTE-NAME. Because of this, git push deletes the branch
on the remote repository.
You might already know that you can "fork" repositories on GitHub.
When you clone a repository you own, you provide it with a remote URL that tells
Git where to fetch and push updates. If you want to collaborate with the original
repository, you'd add a new remote URL, typically called upstream, to
your local Git clone:
git remote add upstream THEIR_REMOTE_URLNow, you can fetch updates and branches from their fork:
git fetch upstream
# Grab the upstream remote's branches
> remote: Counting objects: 75, done.
> remote: Compressing objects: 100% (53/53), done.
> remote: Total 62 (delta 27), reused 44 (delta 9)
> Unpacking objects: 100% (62/62), done.
> From https://{% data variables.product.product_url %}/OCTOCAT/REPO
> * [new branch] main -> upstream/mainWhen you're done making local changes, you can push your local branch to GitHub and initiate a pull request.
For more information on working with forks, see AUTOTITLE.
- The "Remotes" chapter from the "Pro Git" book
git remotemain page- AUTOTITLE
- AUTOTITLE
- Git Handbook{% ifversion fpt or ghec %}
- AUTOTITLE{% endif %}