Skip to content

Latest commit

 

History

History
51 lines (35 loc) · 4.1 KB

pushing-changes-to-github-from-github-desktop.md

File metadata and controls

51 lines (35 loc) · 4.1 KB
title shortTitle intro permissions redirect_from versions
Pushing changes to GitHub from GitHub Desktop
Pushing changes
As you commit changes to your project locally, you can push those changes to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_desktop %} so that others may access them from the remote repository.
People with write permissions can push changes to a repository.
/desktop/contributing-to-projects/pushing-changes-to-github
/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github
/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github
/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop
feature
desktop

About pushing changes to {% data variables.product.prodname_dotcom %}

When you push changes, you send the committed changes in your local repository to the remote repository on {% data variables.product.prodname_dotcom %}. If you change your project locally and want other people to have access to the changes, you must push the changes to {% data variables.product.prodname_dotcom %}.

Before pushing changes, you should update your local branch to include any commits that have been added to the remote repository. If someone has made commits on the remote that are not on your local branch, {% data variables.product.prodname_desktop %} will prompt you to fetch the new commits before pushing your changes to avoid merge conflicts. For more information, see "AUTOTITLE."

{% data reusables.desktop.protected-branches %}

{% ifversion repo-rules %}

Repository administrators can also enable rulesets for a branch, which will prevent a push from completing if a ruleset has not been followed. For example, a ruleset may require a specific branch naming convention, or an issue number at the start of a commit message. {% data variables.product.prodname_desktop %} will warn about rulesets to help prevent your branch from getting into a state where you would be unable to push your changes. For more information, see "AUTOTITLE."

{% endif %}

Pushing changes to {% data variables.product.prodname_dotcom %}

{% note %}

Note: {% data variables.product.prodname_desktop %} will reject a push if it exceeds certain limits.

  • A push contains a large file over {% data variables.large_files.max_github_size %} in size.
  • A push is over {% data variables.large_files.max_file_size %} in total size.

If you configure {% data variables.large_files.product_name_long %} to track your large files, you can push large files that would normally be rejected. For more information, see "AUTOTITLE."

{% endnote %}

{% data reusables.desktop.push-origin %}

  1. If there are commits on the remote branch that you don't have on your local branch, {% data variables.product.prodname_desktop %} prompts you to fetch new commits from the remote. In the "New Commits on Remote" window, click Fetch.

  2. Optionally, click Preview Pull Request to open a preview dialog where you can review your changes and begin to create a pull request. For more information, see "AUTOTITLE."

    Screenshot of the "No local changes" view. A button, labeled "Preview Pull Request", is highlighted with an orange outline.

Further reading