Downloads of v 2.36.0:


Last Update:

20 Apr 2022

Package Maintainer(s):

Software Author(s):

  • The Git Development Community


git vcs dvcs version-control msysgit foss cross-platform cli


This is not the latest version of Git available.

  • 1
  • 2
  • 3

2.36.0 | Updated: 20 Apr 2022



Downloads of v 2.36.0:



Software Author(s):

  • The Git Development Community

  • 1
  • 2
  • 3
Git 2.36.0

This is not the latest version of Git available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Git, run the following command from the command line or from PowerShell:


To upgrade Git, run the following command from the command line or from PowerShell:


To uninstall Git, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade git -y --source="'INTERNAL REPO URL'" --version="'2.36.0'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade git -y --source="'INTERNAL REPO URL'" --version="'2.36.0'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install git
    name: git
    version: '2.36.0'
    state: present

See docs at

chocolatey_package 'git' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.36.0'

See docs at

cChocoPackageInstaller git
    Name     = "git"
    Version  = "2.36.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'git':
  ensure   => '2.36.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 21 Apr 2022.


Git for Windows focuses on offering a lightweight, native set of tools that bring the full feature set of the Git SCM to Windows while providing appropriate user interfaces for experienced Git users and novices alike.


  • Git BASH: Git for Windows provides a BASH emulation used to run Git from the command line. *NIX users should feel right at home, as the BASH emulation behaves just like the "git" command in LINUX and UNIX environments.
  • Git GUI: As Windows users commonly expect graphical user interfaces, Git for Windows also provides the Git GUI, a powerful alternative to Git BASH, offering a graphical version of just about every Git command line function, as well as comprehensive visual diff tools.
  • Shell Integration: Simply right-click on a folder in Windows Explorer to access the BASH or GUI.

Package parameters

  • /GitOnlyOnPath - Puts gitinstall\cmd on path. This is also done by default if no package parameters are set.
  • /GitAndUnixToolsOnPath - Puts gitinstall\bin on path. This setting will override /GitOnlyOnPath.
  • /NoAutoCrlf - Ensure 'Checkout as is, commit as is'. This setting only affects new installs, it will not override an existing .gitconfig.
  • /WindowsTerminal - Makes vim use the regular Windows terminal instead of MinTTY terminal.
  • /NoShellIntegration - Disables open GUI and open shell integration ( "Git GUI Here" and "Git Bash Here" entries in context menus).
  • /NoGuiHereIntegration - Disables open GUI shell integration ( "Git GUI Here" entry in context menus).
  • /NoShellHereIntegration - Disables open git bash shell integration ( "Git Bash Here" entry in context menus).
  • /NoCredentialManager - Disable Git Credential Manager by adding $Env:GCM_VALIDATE='false' user environment variable.
  • /NoGitLfs - Disable Git LFS installation.
  • /SChannel - Configure Git to use the Windows native SSL/TLS implementation (SChannel) instead of OpenSSL. This aligns Git HTTPS behavior with other Windows applications and system components and increases manageability in enterprise environments.
  • /NoOpenSSH - Git will not install its own OpenSSH (and related) binaries but use them as found on the PATH.
  • /WindowsTerminalProfile - Add a Git Bash Profile to Windows Terminal.
  • /Symlinks - Enable symbolic links (requires the SeCreateSymbolicLink permission). Existing repositories are unaffected by this setting.
  • /DefaultBranchName:default_branch_name - Define the default branch name.
  • /Editor:Nano|VIM|Notepad++|VisualStudioCode|VisualStudioCodeInsiders|SublimeText|Atom|VSCodium|Notepad|Wordpad|Custom editor path - Default editor used by Git. The selected editor needs to be available on the machine (unless it is part of git for windows) for this to work.

Experimental parameters

Warning: the following parameters are experimental in the git installer and could stop working at any point.

  • /PseudoConsoleSupport - Enable experimental support for pseudo consoles. Allows running native console programs like Node or Python in a Git Bash window without using winpty, but it still has known bugs.
  • /FSMonitor - Enable experimental built-in file system monitor. Automatically run a built-in file system watcher, to speed up common operations such as git status, git add, git commit, etc in worktrees containing many files.

Example: choco install git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf"


  • The package uses default install options minus cheetah integration and desktop icons. Cheetah prevents a good upgrade scenario, so it has been removed.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Git 2.36.1 91506 Monday, June 13, 2022 Approved
Git 2.36.0 214727 Wednesday, April 20, 2022 Approved
Git 2.35.3 35103 Friday, April 15, 2022 Approved
Git 2.35.2 32502 Tuesday, April 12, 2022 Approved
Git 256923 Tuesday, February 1, 2022 Approved
Git 2.35.1 27386 Saturday, January 29, 2022 Approved
Git 2.35.0 35616 Tuesday, January 25, 2022 Approved
Git 2.34.1 215643 Thursday, November 25, 2021 Approved
Git 2.34.0 56223 Tuesday, November 16, 2021 Approved
Discussion for the Git Package

Ground Rules:

  • This discussion is only about Git and the Git package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Git, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus