# Git > **TL;DR** > `File | Settings | Version Control | Git` for Windows and Linux > > > > `IntelliJ IDEA | Settings | Version Control | Git` for macOS > > > > `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) ![the Settings icon](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.settings.svg) Use this page to specify the version control settings that will be applied to the directories of your project that are under [Git](using-git-integration.html) control. | Path to Git executable | In this field, specify the path to the Git executable file. Type the path or click Browse ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) and specify the path in the dialog that opens. IntelliJ IDEA supports Git from the Windows Subsystem for Linux 2 (WSL2), which is available in [Windows 10 version 2004](https://devblogs.microsoft.com/commandline/wsl2-will-be-generally-available-in-windows-10-version-2004/). If Git is not installed on Windows, IntelliJ IDEA searches for Git in WSL and uses it from there. Also, IntelliJ IDEA automatically switches to Git from WSL for projects that are opened when you use the `\\wsl$` path. ![WSL2 support for Git on Windows](https://resources.jetbrains.com.cn/help/img/idea/2026.2/go_wsl2_support_for_git_on_windows.png) | | Test | Click this button to verify the path to the Git executable file. | ## Commit | Enable staging area | Enable this option if you are more used to the concept of [staging](https://git-scm.com/docs/git-add) changes for commit instead of using [changelists](managing-changelists.html) where modified files are staged automatically. Using the staging area allows you to easily commit changes to the same file separately (including overlapping changes), and see which changes are already staged without switching focus from the editor. For more information, refer to [Use the Git staging area to commit changes](commit-and-push-changes.html#use-git-staging-area-to-commit-changes). > **Note:** > If you enable the staging area, all existing changelists will be deleted. | | Warn if CRLF line separators are about to be committed | Select this option to enable smart handling of `LF` and `CRLF` line separators. IntelliJ IDEA will analyze your configuration, warn you if you are about to commit CRLF into the repository, and suggest changing the `core.autocrlf` setting to `true` or `input` depending on your operating system. > **Note:** > This setting is not applied to files where you have set any related Git attributes. In this case, IntelliJ IDEA assumes that you clearly understand what you are doing and excludes such files from analysis. If this option is deselected, you will have to fix issues with line endings manually using the [Diff Viewer dialog](differences-viewer.html). | | Warn when committing in detached HEAD or during rebase | Select this option if you want IntelliJ IDEA to display a warning when a commit is performed from a detached head or on rebase, as this may cause issues and code loss. | | Add the 'cherry-picked from ' suffix when picking commits pushed to protected branches | Select this option if you want to keep a reference to the original commit when cherry-picking a commit from a [protected branch](https://help.github.com/articles/about-protected-branches/). By default, no suffix is added when cherry-picking a change. | | Configure GPG Key | Click to configure GPG Key for signing your commits or to select an existing key. For more information, refer to [Sign commits with GPG keys](set-up-GPG-commit-signing.html). | ## Push | Auto-update if push of the current branch was rejected | Select this checkbox if you want the current branch to be updated automatically if the `push` operation from the current branch to its tracked branch is rejected. If this option is deselected, IntelliJ IDEA will display the Push Rejected dialog when [pushing a branch](commit-and-push-changes.html#update_when_push_rejected) is rejected because your local repository and the remote storage are not synchronized. Note the following: * If you have never seen the Push Rejected dialog before and you are enabling the checkbox initially, IntelliJ IDEA will update the conflicting local branch silently by means of the `merge` operation. * If you have already encountered the Push Rejected dialog and selected the Remember the update method choice... option, IntelliJ IDEA saves your last choice `rebase` or `merge` and will apply it to update the conflicting local branch silently. Accordingly, to change the "remembered" setting, clear the checkbox, access the Push Rejected dialog, select the Auto-update if push ... rejected option, and invoke another update strategy. | | Show Push dialog for Commit and Push | Select this option if you want the [Push dialog](commit-and-push-changes.html#push) to be displayed after you've clicked Commit and Push in the Commit Changes dialog. Otherwise, your changes will be pushed automatically to the affected repository. | | Show Push dialog only when committing to protected branches | Select this option if you only want to show the [Push Changes](commit-and-push-changes.html#push) dialog if you are pushing to a protected branch when you've clicked Commit and Push in the Commit Changes dialog. Otherwise, your changes will be pushed automatically to the affected repository. | | Protected branches | If you want to disable the ability to [force push changes](commit-and-push-changes.html#force-push) for certain branches, list them here (this is a team-shared parameter that is stored in `.idea/vcs.xml`). You can list several branches separated by a semicolon, or supply branch patterns as the input is treated as a list of regular expressions. | | Load branch protection rules from GitHub | Select this option if you want to add GitHub protection rules to IntelliJ IDEA and sync them on every fetch. | ## Update | Update method | Use this list to choose the strategy to synchronize your local repository with the remote storage. The selected method will be used when the `push` operation is rejected (if the [Auto-updated if push of the current branch was rejected](#autoUpdate) option is enabled), or when you invoke the Update Project operation. The following options are available: * Merge: select this option to perform [merge](http://schacon.github.io/git/git-merge.html) during the update. This is equivalent to running `git fetch` and then `git merge`, or `git pull --no-rebase`. * Rebase: select this option to perform [rebase](http://schacon.github.io/git/git-rebase.html) during the update. This is equivalent to running `git fetch` and then `git rebase`, or `git pull --rebase` (all local commits will be put on top of the updated upstream head). | | Clean working tree using | Select how you want uncommitted changes to be treated when you perform a project update: * Stash: local changes will be saved to a [git stash](shelving-and-unshelving-changes.html#stash). This is useful if you need to apply patches with stashed changes outside IntelliJ IDEA, as they are generated by Git itself. * Shelve: IntelliJ IDEA will put local changes to a [shelf](shelving-and-unshelving-changes.html#shelve-unshelve-changes). Shelving is done by IntelliJ IDEA, and patches generated from shelved changes are normally applied inside IntelliJ IDEA. | | Filter "Update Project" information by paths | If you don't want to get information on all changes to a project in the [Update Info](version-control-tool-window-update-info-tab.html) tab when you perform an [update](sync-with-a-remote-repository.html#update), you can filter the list by specific paths. | | Fetch remote changes automatically | Enables background fetching of remote updates every 20 minutes. Use this to keep track of incoming changes. The interval is configurable via the `git.update.incoming.info.time` registry key. | | Check remote for incoming changes | When this option is enabled, IntelliJ IDEA will check if there are pending incoming commits that have not been fetched to your local repository, and will mark such branches in the VCS widget. | | Fetch tags | Specify how IntelliJ IDEA should handle tags when fetching from a remote: * Auto: follows the default behavior defined in your Git configuration. * Sync (`--prune-tags`): fetches all tags from the remote and deletes local tags that no longer exist on the remote repository. * Always (`--tags`): forces the fetching of all tags from the remote. * Never (`--no-tags`): disables tag fetching entirely. | | Use credential helper | Select this option if you don't want to override [credential helpers](https://git-scm.com/docs/gitcredentials), which is the default behavior. You will be able to authenticate using a credential helper in the Git login dialog. | ## Stash | Combine stashes and shelves in one tab | Enable this option if you want to see both [stashed](shelving-and-unshelving-changes.html#stash) and [shelved](shelving-and-unshelving-changes.html#shelve-unshelve-changes) changes listed in one tab called Stashes and Shelves in the Commit tool window (`Alt+0` (Windows), `⌘ 0` (macOS), `⌘ 0` (IntelliJ IDEA Classic (macOS)), `⌘ 0` (macOS System Shortcuts), `Alt+0` (XWin), `Alt+0` (GNOME), `Alt+0` (KDE), `Alt+0` (Emacs), `Alt+0` (Sublime Text), `⌘ 0` (Sublime Text (macOS)), `Alt+0` (NetBeans), `Alt+0` (Visual Studio), `Alt+0` (Visual Studio (macOS)), `Alt+0` (Eclipse), `⌘ 0` (Eclipse (macOS)) ) . | | When "Show Diff" is called, compare stashed changes | In this section, specify what you want to see in the Diff viewer while investigating the stashed changes. * With the local version of a file: stashed changes are compared with the local version of the selected file. This option is enabled by default. * With the parent commit: stashed changes are compared with the parent commit. | ## See also ### Procedures [Version control](version-control-integration.html) [Git](using-git-integration.html)