Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

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

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

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

Webinar from
Wednesday, 17 January 2024

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!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
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



Downloads of v


Last Update:

15 Dec 2015

Package Maintainer(s):

Software Author(s):

  • Various


git configuration alias

Git - Config

  • 1
  • 2
  • 3 | Updated: 15 Dec 2015



Downloads of v



Software Author(s):

  • Various

Git - Config

  • 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 - Config, run the following command from the command line or from PowerShell:


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


To uninstall Git - Config, 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 https://community.chocolatey.org/api/v2/)

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 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. Copy Your Script

choco upgrade jivkok.gitconfig -y --source="'INTERNAL REPO 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 jivkok.gitconfig -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install jivkok.gitconfig
    name: jivkok.gitconfig
    version: ''
    state: present

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

chocolatey_package 'jivkok.gitconfig' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

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

cChocoPackageInstaller jivkok.gitconfig
    Name     = "jivkok.gitconfig"
    Version  = ""
    Source   = "INTERNAL REPO URL"

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

package { 'jivkok.gitconfig':
  ensure   => '',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.


This package is exempt from moderation. While it is likely safe for you, there is more risk involved.


Jivko's standard Git configuration and aliases:

  • core config
  • colors (status/diff/branches)
  • diff tool
  • merge tool
  • aliases (amend, branch, commit, checkout, diff, log, rebase, reset, status)

$package = 'jivkok.GitConfig'

# inspired by
# https://git.wiki.kernel.org/index.php/Aliases
# https://gist.github.com/bradwilson/4215933
# https://gist.github.com/oli/1637874

# Prereqs

$git_exe = 'git.exe'
if ((Get-Command $git_exe -ErrorAction SilentlyContinue) -eq $null)
  if (Test-Path "${env:ProgramW6432}\Git\bin\git.exe")
    $git_exe = "${env:ProgramW6432}\Git\bin\git.exe"
  elseif (Test-Path "${env:ProgramFiles(x86)}\Git\bin\git.exe")
    $git_exe = "${env:ProgramFiles(x86)}\Git\bin\git.exe"
    throw 'Could not find git.exe'
Write-Output "Found Git: $git_exe"

setx TERM cygwin /M
$kdiffPath = "$env:ProgramW6432\KDiff3\kdiff3.exe"
if (Test-Path $kdiffPath) { Write-Output "Found KDiff3 at: $kdiffPath" } else { Write-Warning "Could not find KDiff3 at: $kdiffPath" }

# Core
. $git_exe config --global core.autocrlf true
. $git_exe config --global core.preloadindex true
. $git_exe config --global core.fscache true
. $git_exe config --global core.safecrlf false
$defaultEditor = . $git_exe config --get core.editor
if (!$defaultEditor)
  . $git_exe config --global core.editor notepad
. $git_exe config --global help.format html
. $git_exe config --global pack.packSizeLimit 2g
. $git_exe config --global push.default current
. $git_exe config --global rebase.autosquash true

# Colors
. $git_exe config --global color.branch.current "red bold"
. $git_exe config --global color.branch.local normal
. $git_exe config --global color.branch.remote "yellow bold"
. $git_exe config --global color.branch.plain normal
. $git_exe config --global color.diff.meta "yellow bold"
. $git_exe config --global color.diff.frag "magenta bold"
. $git_exe config --global color.diff.old "red bold"
. $git_exe config --global color.diff.new "green bold"
. $git_exe config --global color.status.header normal
. $git_exe config --global color.status.new "red bold"
. $git_exe config --global color.status.added "green bold"
. $git_exe config --global color.status.updated "cyan bold"
. $git_exe config --global color.status.changed "cyan bold"
. $git_exe config --global color.status.untracked "red bold"
. $git_exe config --global color.status.nobranch "red bold"

# Diff & Merge
if (Test-Path $kdiffPath)
  . $git_exe config --global diff.tool kdiff3
  . $git_exe config --global diff.guitool kdiff3
  . $git_exe config --global difftool.prompt false
  . $git_exe config --global difftool.kdiff3.path "$kdiffPath"
  . $git_exe config --global difftool.kdiff3.keepBackup false
  . $git_exe config --global difftool.kdiff3.trustExitCode false

  . $git_exe config --global merge.tool kdiff3
  . $git_exe config --global mergetool.prompt false
  . $git_exe config --global mergetool.kdiff3.path "$kdiffPath"
  . $git_exe config --global mergetool.kdiff3.keepBackup false
  . $git_exe config --global mergetool.kdiff3.trustExitCode false

# Aliases
. $git_exe config --global alias.a 'add -A'
. $git_exe config --global alias.aliases 'config --get-regexp alias'
. $git_exe config --global alias.amend 'commit --amend -C HEAD'
. $git_exe config --global alias.bl 'blame -w -M -C'
. $git_exe config --global alias.br 'branch'
. $git_exe config --global alias.bra 'branch -rav'
. $git_exe config --global alias.branches 'branch -rav'
. $git_exe config --global alias.cat 'cat-file -t'
. $git_exe config --global alias.cm 'commit -m'
. $git_exe config --global alias.co 'checkout'
. $git_exe config --global alias.df 'diff --word-diff=color --word-diff-regex=. -w --patience'
. $git_exe config --global alias.dump 'cat-file -p'
. $git_exe config --global alias.files '! git ls-files | grep -i'
. $git_exe config --global alias.filelog 'log -u'
. $git_exe config --global alias.hist "log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue) [%an]%Creset' --abbrev-commit --date=relative"
. $git_exe config --global alias.l 'log --pretty=format:\"%h %ad | %s%d [%an]\" --date=short'
. $git_exe config --global alias.last 'log -p --max-count=1 --word-diff'
. $git_exe config --global alias.lastref 'rev-parse --short HEAD'
. $git_exe config --global alias.lasttag 'describe --tags --abbrev=0'
. $git_exe config --global alias.lg 'log --pretty=format:\"%h %ad | %s%d [%an]\" --graph --date=short'
. $git_exe config --global alias.loglist 'log --oneline'
. $git_exe config --global alias.pick 'add -p'
. $git_exe config --global alias.pp 'pull --prune'
. $git_exe config --global alias.pullom 'pull origin master'
. $git_exe config --global alias.pushom 'push origin master'
. $git_exe config --global alias.re 'rebase'
. $git_exe config --global alias.reabort 'rebase --abort'
. $git_exe config --global alias.rego 'rebase --continue'
. $git_exe config --global alias.reskip 'rebase --skip'
. $git_exe config --global alias.remotes 'remote -v show'
. $git_exe config --global alias.st 'status -sb'
. $git_exe config --global alias.stats 'diff --stat'
. $git_exe config --global alias.undo 'reset HEAD~'
. $git_exe config --global alias.unstage 'reset HEAD'
. $git_exe config --global alias.wdiff 'diff --word-diff'
. $git_exe config --global alias.who 'shortlog -s -e --'
. $git_exe config --global alias.zap 'reset --hard HEAD'
$userName = . $git_exe config --global --get user.name
if ($userName)
  . $git_exe config --global alias.standup "log --since yesterday --oneline --author $userName"
  Write-Warning "Set git global username with git config --global user.name 'foo' to use standup"
Write-Host "Manually edit $ENV:USERPROFILE\.gitconfig to revert package changes"

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 - Config 398 Saturday, December 12, 2015 Exempted
Git - Config 835 Tuesday, May 6, 2014 Exempted
Git - Config 486 Monday, May 5, 2014 Unknown
Git - Config 520 Monday, May 5, 2014 Unknown
Git - Config 450 Monday, May 5, 2014 Unknown
Discussion for the Git - Config Package

Ground Rules:

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