Downloads:

5,651,989

Downloads of v 2.14.2.20170927:

180,510

Last Update:

27 Sep 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.

  • 1
  • 2
  • 3

2.14.2.20170927 | Updated: 27 Sep 2017

Downloads:

5,651,989

Downloads of v 2.14.2.20170927:

180,510

Maintainer(s):

Software Author(s):

  • The Git Development Community

Tags:

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

  • 1
  • 2
  • 3
 Git 2.14.2.20170927

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

Details

Scan Testing Successful:

No detections found in any package files

Details

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

  • 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://community.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

3. Enter your internal repository url

(this should look similar to https://community.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.14.2.20170927
    source: STEP 3 URL

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


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

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


Chocolatey::Ensure-Package
(
    Name: git,
    Version: 2.14.2.20170927,
    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.14.2.20170927'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install git version="2.14.2.20170927" 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 27 Sep 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

  • /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).
  • /NoCredentialManager - Disable Git Credential Manager by adding $Env:GCM_VALIDATE='false' user environment variable.
  • /NoGitLfs - Disable Git LFS installation.

Notes

  • 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.

Version Downloads Last Updated Status
Git 2.32.0.2 92090 Wednesday, July 7, 2021 Approved
Git 2.32.0 124996 Monday, June 7, 2021 Approved
Git 2.31.1 235476 Saturday, March 27, 2021 Approved
Git 2.31.0 89417 Tuesday, March 16, 2021 Approved
Git 2.30.2 46998 Tuesday, March 9, 2021 Approved
Git 2.30.1 110981 Tuesday, February 9, 2021 Approved
Git 2.30.0.2 97113 Thursday, January 14, 2021 Approved
Git 2.30.0 59888 Tuesday, December 29, 2020 Approved
Git 2.29.2.3 67665 Tuesday, December 8, 2020 Approved
Git 2.29.2.2 303198 Thursday, November 5, 2020 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