Downloads:

3,454,980

Downloads of v 2.5.3:

7,129

Last Update:

18 Sep 2015

Package Maintainer(s):

Software Author(s):

  • Johannes Schindelin
  • msysgit Committers

Tags:

git vcs dvcs version control msysgit admin

Git

This is not the latest version of Git available.

2.5.3 | Updated: 18 Sep 2015

Downloads:

3,454,980

Downloads of v 2.5.3:

7,129

Maintainer(s):

Software Author(s):

  • Johannes Schindelin
  • msysgit Committers

Tags:

git vcs dvcs version control msysgit admin

Git 2.5.3

This is not the latest version of Git available.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

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://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://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.5.3
    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.5.3'
  source   'STEP 3 URL'
end

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


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

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


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

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


salt '*' chocolatey.install git version="2.5.3" 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 18 Sep 2015.

Description

Git (for Windows) - Git is a powerful distributed Source Code Management tool. If you just want to use Git to do your version control in Windows, you will need to download Git for Windows, run the installer, and you are ready to start.

Note: Git for Windows is a project run by volunteers, so if you want it to improve, volunteer!

Package Specifics

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

Package Parameters

The following package parameters can be set:

  • /GitOnlyOnPath - this puts gitinstall\cmd on path. This is also done by default if no package parameters are set.
  • /GitAndUnixToolsOnPath - this puts gitinstall\bin on path. This setting will override /GitOnlyOnPath.
  • /NoAutoCrlf - this setting only affects new installs, it will not override an existing .gitconfig. This will ensure 'Checkout as is, commit as is'

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

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.25.0 53534 Tuesday, January 14, 2020 Approved
Git 2.24.1.2 95373 Wednesday, December 11, 2019 Approved
Git 2.24.0.2 53626 Thursday, November 7, 2019 Approved
Git 2.24.0 74310 Tuesday, November 5, 2019 Approved
Git 2.23.0 227608 Sunday, August 18, 2019 Approved
Git 2.22.0 180592 Saturday, June 8, 2019 Approved
Git 2.21.0 208140 Wednesday, February 27, 2019 Approved
Git 2.20.1 134178 Saturday, December 15, 2018 Approved
Git 2.20.0 18891 Monday, December 10, 2018 Approved
Git 2.19.2 38178 Thursday, November 22, 2018 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