Downloads:

3,096,083

Downloads of v 2.11.1:

7,167

Last Update:

2/3/2017

Package Maintainer(s):

Software Author(s):

The Git Development Community

Tags:

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

Git

This is not the latest version of Git available.

2.11.1 | Updated: 2/3/2017

Downloads:

3,096,083

Downloads of v 2.11.1:

7,167

Maintainer(s):

Software Author(s):

The Git Development Community

Tags:

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

Git 2.11.1

This is not the latest version of Git available.

All Checks are Passing

2 Passing Test

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Individual
Organization

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:

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

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 https://chocolatey.org/api/v2. 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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the Package Download
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run choco download git --internalize --version=2.11.1 --source=https://chocolatey.org/api/v2 (additional options)
- Run choco push --source="'http://internal/odata/repo'" for package and dependencies
- Automate package internalization

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade git -y --source="'STEP 3 URL'" [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="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Ensure git installed
  win_chocolatey:
    name: git
    state: present
    version: 2.11.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'git' do
  action    :install
  version  '2.11.1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: git,
    Version: 2.11.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller git
{
   Name     = 'git'
   Ensure   = 'Present'
   Version  = '2.11.1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'git':
  provider => 'chocolatey',
  ensure   => '2.11.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install git version="2.11.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. 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 2/3/2017.

Description

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.

Features

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

The following package parameters can be set:

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 shell integration ( "Git GUI Here" and "Git Bash Here" entries in context menus).

These parameters can be passed to the installer with the use of -params.
For example: -params '"/GitAndUnixToolsOnPath /NoAutoCrlf"'.

Notes

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

Files

Virus Scan Results

git.2.11.1.nupkg (743d461e46ac) - ## / 58 - 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.

Version History

Version	Downloads	Last Updated	Status
Git 2.23.0	166458	Sunday, August 18, 2019	Approved
Git 2.22.0	179348	Saturday, June 8, 2019	Approved
Git 2.21.0	207336	Wednesday, February 27, 2019	Approved
Git 2.20.1	133491	Saturday, December 15, 2018	Approved
Git 2.20.0	18850	Monday, December 10, 2018	Approved
Git 2.19.2	38135	Thursday, November 22, 2018	Approved
Git 2.19.1	101719	Friday, October 5, 2018	Approved
Git 2.19.0	100714	Thursday, September 13, 2018	Approved
Git 2.18.0	187625	Friday, June 22, 2018	Approved
Git 2.17.1.2	146731	Wednesday, May 30, 2018	Approved
Git 2.17.1	4751	Tuesday, May 29, 2018	Approved
Git 2.17.0	86391	Tuesday, April 3, 2018	Approved
Git 2.16.3	20740	Friday, March 23, 2018	Approved
Git 2.16.2	52092	Tuesday, February 20, 2018	Approved
Git 2.16.1.4	54607	Thursday, February 8, 2018	Approved
Git 2.16.1.3	2919	Tuesday, February 6, 2018	Approved
Git 2.16.1.2	11227	Saturday, February 3, 2018	Approved
Git 2.16.1	22653	Monday, January 22, 2018	Approved
Git 2.16.0.2	9718	Friday, January 19, 2018	Approved
Git 2.15.1.2	61319	Thursday, November 30, 2017	Approved
Git 2.15.1	4292	Wednesday, November 29, 2017	Approved
Git 2.15.0	158980	Monday, October 30, 2017	Approved
Git 2.14.3	36392	Tuesday, October 24, 2017	Approved
Git 2.14.2.20170927	180353	Wednesday, September 27, 2017	Approved
Git 2.14.2	5397	Tuesday, September 26, 2017	Approved
Git 2.14.1	59332	Thursday, August 10, 2017	Approved
Git 2.14.0.2	8303	Monday, August 7, 2017	Approved
Git 2.14.0	4839	Sunday, August 6, 2017	Approved
Git 2.13.3	23788	Friday, July 14, 2017	Approved
Git 2.13.2	20816	Tuesday, June 27, 2017	Approved
Git 2.13.1.2	19739	Friday, June 16, 2017	Approved
Git 2.13.1	4783	Wednesday, June 14, 2017	Approved
Git 2.13.0	93109	Wednesday, May 10, 2017	Approved
Git 2.12.2.2	66907	Wednesday, April 5, 2017	Approved
Git 2.12.2	14139	Tuesday, March 28, 2017	Approved
Git 2.12.1	15589	Tuesday, March 21, 2017	Approved
Git 2.12.0	47171	Saturday, February 25, 2017	Approved
Git 2.11.1.20170208	17238	Wednesday, February 8, 2017	Approved
Git 2.11.1	7167	Friday, February 3, 2017	Approved
Git 2.11.0.3	46504	Saturday, January 14, 2017	Approved
Git 2.11.0.2	1786	Friday, January 13, 2017	Approved
Git 2.11.0	30788	Thursday, December 1, 2016	Approved
Git 2.10.2	23883	Wednesday, November 2, 2016	Approved
Git 2.10.1	25593	Tuesday, October 4, 2016	Approved
Git 2.10.0	21414	Saturday, September 3, 2016	Approved
Git 2.9.3	16646	Saturday, August 13, 2016	Approved
Git 2.9.2	13727	Sunday, July 17, 2016	Approved
Git 2.9.0	804	Tuesday, June 14, 2016	Approved
Git 2.8.4	600	Wednesday, June 8, 2016	Approved
Git 2.8.3	444	Friday, May 20, 2016	Approved
Git 2.8.2	457	Sunday, May 8, 2016	Approved
Git 2.8.1	18075	Tuesday, April 5, 2016	Approved
Git 2.8.0	6263	Tuesday, March 29, 2016	Approved
Git 2.7.4	7825	Friday, March 18, 2016	Approved
Git 2.7.3	3377	Tuesday, March 15, 2016	Approved
Git 2.7.2	13468	Tuesday, February 23, 2016	Approved
Git 2.7.1	10035	Sunday, February 7, 2016	Approved
Git 2.7.0	110127	Tuesday, January 5, 2016	Approved
Git 2.6.4	10462	Monday, December 14, 2015	Approved
Git 2.6.3	17013	Tuesday, November 10, 2015	Approved
Git 2.6.2	13496	Monday, October 19, 2015	Approved
Git 2.6.1	8742	Tuesday, October 6, 2015	Approved
Git 2.6.0	4425	Tuesday, September 29, 2015	Approved
Git 2.5.3	7110	Friday, September 18, 2015	Approved
Git 2.5.2	5534	Friday, September 11, 2015	Approved
Git 2.5.1	7024	Monday, August 31, 2015	Approved
Git 2.5.0	7196	Tuesday, August 18, 2015	Approved
Git 1.9.5.20150320	71965	Wednesday, April 29, 2015	Approved
Git 1.9.5.20150319	16837	Monday, March 23, 2015	Approved
Git 1.9.5.20150114	29485	Wednesday, January 14, 2015	Approved
Git 1.9.5	11255	Thursday, December 18, 2014	Approved
Git 1.9.4.20140929	28411	Monday, September 29, 2014	Approved
Git 1.9.4	34365	Friday, June 13, 2014	Approved
Git 1.9.2	3468	Wednesday, June 4, 2014	Approved
Git 1.9.0.20140303	13364	Tuesday, April 1, 2014	Approved
Git 1.9.0	9209	Tuesday, February 18, 2014	Approved
Git 1.8.5.2	9097	Tuesday, December 31, 2013	Approved
Git 1.8.4	12450	Tuesday, September 17, 2013	Approved
Git 1.8.3	9682	Friday, June 8, 2012	Approved
Git 1.8.1.2	8546	Saturday, February 2, 2013	Approved
Git 1.8.0	4970	Tuesday, October 23, 2012	Approved
Git 1.7.11	3801	Thursday, June 21, 2012	Approved
Git 1.7.10	1202	Sunday, May 27, 2012	Approved

Dependencies

- git.install (= 2.11.1)

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.