Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Learn More Register Now

Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 2.33.1:


Last Update:

14 Oct 2021

Package Maintainer(s):

Software Author(s):

  • The Git Development Community


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

Git (Portable)

This is not the latest version of Git (Portable) available.

  • 1
  • 2
  • 3

2.33.1 | Updated: 14 Oct 2021



Downloads of v 2.33.1:



Software Author(s):

  • The Git Development Community

Git (Portable) 2.33.1

This is not the latest version of Git (Portable) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


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


Deployment Method:


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.portable -y --source="'INTERNAL REPO URL'" --version="'2.33.1'" [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.portable -y --source="'INTERNAL REPO URL'" --version="'2.33.1'" 

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

Exit $exitCode

- name: Install git.portable
    name: git.portable
    version: '2.33.1'
    state: present

See docs at

chocolatey_package 'git.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.33.1'

See docs at

cChocoPackageInstaller git.portable
    Name     = "git.portable"
    Version  = "2.33.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'git.portable':
  ensure   => '2.33.1',
  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.

Package Approved

This package was approved as a trusted package on 14 Oct 2021.


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.


 Note that the only valid version of the GPL as far as this project
 is concerned is _this_ particular version of the license (ie v2, not
 v2.2 or v3.x or whatever), unless explicitly otherwise stated.

 HOWEVER, in order to allow a migration to GPLv3 if that seems like
 a good idea, I also ask that people involved with the project make
 their preferences known. In particular, if you trust me to make that
 decision, you might note so in your copyright message, ie something

	This file is licensed under the GPL v2, or a later version
	at the discretion of Linus.

  might avoid issues. But we can also just decide to synchronize and
  contact all copyright holders on record if/when the occasion arises.

			Linus Torvalds


		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.


  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.


  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.





	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License along
    with this program; if not, write to the Free Software Foundation, Inc.,
    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.
md5: 6BF59EA3825E3A7348DA1C18C9530D26 | sha1: 0BC66A9AE974B6839BD08E489911CC078BD4CD96 | sha256: 723C879EB447583B893AA3234EAE8CAAA77D9D3ECF90883271FBA98E8B2D99AC | sha512: A6170C3548A7B4329D435AAE5E6EDD3B0F8FB8D157B7217C71CE70124FB086ED4D4C13351AF9A8287CEFD78A43CC7314F426496878C00DB638A6D15147AAD652
md5: 5ABF37CBE1629FD58DC67EE0C88F5502 | sha1: AC58D447A3745C115242FDF1412216C60AAA5641 | sha256: FAD2F32A3CA6E39CFBF7258C485A5601B0BFB620F44C582C1BA22784DD3FAAD3 | sha512: 04AEDA4C3A791E47DDFC75B0D5D635A2E5E7D2B92E00B164AF4C080DFC9DA991ED76BDA6713367A10312A376343EA965E2F8AEB0DFAEC5DE907BAA277551B497
$ErrorActionPreference = 'Stop'

$installLocation = Join-Path $(Get-ToolsLocation) 'git'

Write-Host "Removing Git from the '$installLocation'"
Remove-Item $installLocation -Recurse -Force -ea 0

$newPath = $Env:Path.Replace(";$installLocation\bin", '')
if ($newPath -eq $Env:PATH) { return }
# If the package was installed in non-admin mode
# we probably won't ever get here
Write-Host "Removing Git from system PATH"
[System.Environment]::SetEnvironmentVariable('PATH', $newPath, 'Machine')
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path $MyInvocation.MyCommand.Definition

$packageArgs = @{
  PackageName    = 'git.portable'
  FileFullPath   = Get-Item $toolsPath\*-32-bit.7z.exe
  FileFullPath64 = Get-Item $toolsPath\*-64-bit.7z.exe
  Destination    = "$(Get-ToolsLocation)\git"
Get-ChocolateyUnzip @packageArgs
Install-ChocolateyPath "$($packageArgs.Destination)\bin"

Get-ChildItem $toolsPath\*.exe | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" '' } }
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from GitHub and can be verified like this:

1. Download the following installers:
  32-Bit: <>
  64-Bit: <>
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: 
  checksum32: FAD2F32A3CA6E39CFBF7258C485A5601B0BFB620F44C582C1BA22784DD3FAAD3
  checksum64: 723C879EB447583B893AA3234EAE8CAAA77D9D3ECF90883271FBA98E8B2D99AC

File 'LICENSE.txt' is obtained from <>

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 (Portable) 2.42.0 3404 Tuesday, August 22, 2023 Approved
Git (Portable) 2.41.0 1020 Thursday, June 1, 2023 Approved
Git (Portable) 2.40.1 2309 Tuesday, April 25, 2023 Approved
Git (Portable) 2.40.0 768 Tuesday, March 14, 2023 Approved
Git (Portable) 2.39.2 1187 Wednesday, February 15, 2023 Approved
Git (Portable) 2.39.1 1254 Wednesday, January 18, 2023 Approved
Git (Portable) 2.39.0 1207 Monday, December 12, 2022 Approved
Git (Portable) 2.38.1 1769 Wednesday, October 19, 2022 Approved
Git (Portable) 2.37.3 1967 Wednesday, August 31, 2022 Approved
Git (Portable) 748 Friday, August 12, 2022 Approved
Git (Portable) 2.37.1 1102 Tuesday, July 12, 2022 Approved
Git (Portable) 2.37.0 653 Tuesday, June 28, 2022 Approved
Git (Portable) 2.36.1 1778 Tuesday, May 10, 2022 Approved
Git (Portable) 2.36.0 1459 Wednesday, April 20, 2022 Approved
Git (Portable) 2.35.3 358 Friday, April 15, 2022 Approved
Git (Portable) 2.35.2 356 Tuesday, April 12, 2022 Approved
Git (Portable) 2448 Tuesday, February 1, 2022 Approved
Git (Portable) 2.35.1 303 Saturday, January 29, 2022 Approved
Git (Portable) 2.35.0 738 Tuesday, January 25, 2022 Approved
Git (Portable) 2.34.1 1584 Thursday, November 25, 2021 Approved
Git (Portable) 2.34.0 871 Tuesday, November 16, 2021 Approved
Git (Portable) 2.33.1 3557 Thursday, October 14, 2021 Approved
Git (Portable) 2798 Tuesday, August 24, 2021 Approved
Git (Portable) 2217 Wednesday, July 7, 2021 Approved
Git (Portable) 2.32.0 1185 Monday, June 7, 2021 Approved
Git (Portable) 2.31.1 4037 Saturday, March 27, 2021 Approved
Git (Portable) 2.31.0 1036 Tuesday, March 16, 2021 Approved
Git (Portable) 2.30.2 744 Tuesday, March 9, 2021 Approved
Git (Portable) 2.30.1 1893 Tuesday, February 9, 2021 Approved
Git (Portable) 1306 Thursday, January 14, 2021 Approved
Git (Portable) 2.30.0 1091 Tuesday, December 29, 2020 Approved
Git (Portable) 2.29.2 2275 Friday, October 30, 2020 Approved
Git (Portable) 2.29.1 616 Saturday, October 24, 2020 Approved
Git (Portable) 2.29.0 427 Tuesday, October 20, 2020 Approved
Git (Portable) 2.28.0 2142 Friday, July 31, 2020 Approved
Git (Portable) 2.27.0 1655 Tuesday, June 2, 2020 Approved
Git (Portable) 2.26.2 1623 Monday, April 20, 2020 Approved
Git (Portable) 2.26.1 487 Wednesday, April 15, 2020 Approved
Git (Portable) 2.26.0 1003 Tuesday, March 24, 2020 Approved
Git (Portable) 2.25.1 1510 Thursday, February 20, 2020 Approved
Git (Portable) 2.25.0 1824 Tuesday, January 14, 2020 Approved
Git (Portable) 1291 Wednesday, December 11, 2019 Approved
Git (Portable) 792 Monday, November 11, 2019 Approved
Git (Portable) 2.24.0 386 Tuesday, November 5, 2019 Approved
Git (Portable) 2.23.0 1763 Thursday, August 22, 2019 Approved
Git (Portable) 2.22.0 5838 Saturday, June 8, 2019 Approved
Git (Portable) 2.21.0 3175 Wednesday, February 27, 2019 Approved
Git (Portable) 2.20.1 14795 Sunday, December 16, 2018 Approved
Git (Portable) 2.20.0 2932 Monday, December 10, 2018 Approved
Git (Portable) 2.19.2 7835 Thursday, November 22, 2018 Approved
Git (Portable) 2.19.1 16734 Friday, October 5, 2018 Approved
Git (Portable) 2.19.0 4947 Thursday, September 13, 2018 Approved
Git (Portable) 2.18.0 1197 Friday, June 22, 2018 Approved
Git (Portable) 792 Wednesday, May 30, 2018 Approved
Git (Portable) 2.17.1 360 Tuesday, May 29, 2018 Approved
Git (Portable) 2.17.0 989 Tuesday, April 3, 2018 Approved
Git (Portable) 2.16.3 631 Friday, March 23, 2018 Approved
Git (Portable) 2.16.2 824 Wednesday, February 21, 2018 Approved
Git (Portable) 601 Thursday, February 8, 2018 Approved
Git (Portable) 458 Tuesday, February 6, 2018 Approved
Git (Portable) 472 Saturday, February 3, 2018 Approved
Git (Portable) 2.16.1 598 Tuesday, January 23, 2018 Approved
Git (Portable) 486 Friday, January 19, 2018 Approved
Git (Portable) 1024 Thursday, November 30, 2017 Approved
Git (Portable) 2.15.1 464 Wednesday, November 29, 2017 Approved
Git (Portable) 486 Sunday, November 26, 2017 Approved
Git (Portable) 2.15.0 735 Monday, October 30, 2017 Approved
Git (Portable) 2.14.3 539 Tuesday, October 24, 2017 Approved
Git (Portable) 607 Friday, October 13, 2017 Approved
Git (Portable) 542 Friday, October 6, 2017 Approved
Git (Portable) 2.14.2 631 Tuesday, September 26, 2017 Approved
Git (Portable) 2.14.1 902 Thursday, August 10, 2017 Approved
Git (Portable) 494 Monday, August 7, 2017 Approved
Git (Portable) 2.14.0 506 Sunday, August 6, 2017 Approved
Git (Portable) 2.13.3 598 Friday, July 14, 2017 Approved
Git (Portable) 2.13.2 665 Tuesday, June 27, 2017 Approved
Git (Portable) 542 Friday, June 16, 2017 Approved
Git (Portable) 2.13.1 460 Wednesday, June 14, 2017 Approved
Git (Portable) 2.13.0 911 Wednesday, May 10, 2017 Approved
Git (Portable) 817 Wednesday, April 5, 2017 Approved
Git (Portable) 2.12.2 577 Tuesday, March 28, 2017 Approved
Git (Portable) 2.12.1 593 Tuesday, March 21, 2017 Approved
Git (Portable) 2.12.0 716 Sunday, February 26, 2017 Approved
Git (Portable) 2.11.1 761 Friday, February 3, 2017 Approved
Git (Portable) 458 Saturday, January 14, 2017 Approved
Git (Portable) 420 Friday, January 13, 2017 Approved
Git (Portable) 2.11.0 391 Wednesday, January 18, 2017 Approved

Discussion for the Git (Portable) Package

Ground Rules:

  • This discussion is only about Git (Portable) and the Git (Portable) 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 (Portable), 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