Downloads:

2,608

Downloads of v 0.0.3:

349

Last Update:

4/5/2013

Package Maintainer(s):

Software Author(s):

  • Various

Tags:

Git

Git - Aliases

This is not the latest version of Git - Aliases available.

0.0.3 | Updated: 4/5/2013

Downloads:

2,608

Downloads of v 0.0.3:

349

Maintainer(s):

Software Author(s):

  • Various

Tags:

Git

Git - Aliases 0.0.3

This is not the latest version of Git - Aliases available.

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

To install Git - Aliases, run the following command from the command line or from PowerShell:

>

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

>

To uninstall Git - Aliases, 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 ethanbrown.gitaliases -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 ethanbrown.gitaliases -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 ethanbrown.gitaliases installed
  win_chocolatey:
    name: ethanbrown.gitaliases
    state: present
    version: 0.0.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 'ethanbrown.gitaliases' do
  action    :install
  version  '0.0.3'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: ethanbrown.gitaliases,
    Version: 0.0.3,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller ethanbrown.gitaliases
{
   Name     = 'ethanbrown.gitaliases'
   Ensure   = 'Present'
   Version  = '0.0.3'
   Source   = 'STEP 3 URL'
}

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


package { 'ethanbrown.gitaliases':
  provider => 'chocolatey',
  ensure   => '0.0.3',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install ethanbrown.gitaliases version="0.0.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 was submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.

Description

My standard Git aliases

  aliases = config --get-regexp alias
  amend = commit --amend
  bl = blame -w -M -C
  bra = git branch -rav
  branches = git branch -rav
  changed = status -sb
  f = !git ls-files | grep -i
  filelog = log -u
  hist = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue) [%an]%Creset' --abbrev-commit --date=relative
  last = log -p --max-count=1 --word-diff
  lasttag = describe --tags --abbrev=0
  pick = add -p
  remotes = remote -v show
  stage = add
  standup = log --since yesterday --oneline --author {ME}
  stats = diff --stat
  sync = ! git fetch upstream -v && git fetch origin -v && git checkout master && git merge upstream/master
  undo = reset head~
  unstage = reset HEAD
  wdiff = diff --word-diff
  who = shortlog -s -e --

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 - Aliases 0.0.4 336 Thursday, April 25, 2013 Unknown
Git - Aliases 0.0.3 349 Friday, April 5, 2013 Unknown
Git - Aliases 0.0.2 375 Tuesday, March 19, 2013 Unknown
Git - Aliases 0.0.1 371 Tuesday, March 12, 2013 Unknown
Discussion for the Git - Aliases Package

Ground Rules:

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