Downloads:

4,068

Downloads of v 1.2.0:

1,209

Last Update:

27 Oct 2013

Package Maintainer(s):

Software Author(s):

  • Various

Tags:

Git

Tim Rayburn's GIT Aliases

1.2.0 | Updated: 27 Oct 2013

Downloads:

4,068

Downloads of v 1.2.0:

1,209

Maintainer(s):

Software Author(s):

  • Various

Tags:

Git

Tim Rayburn's GIT Aliases 1.2.0

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test


Validation Testing Unknown


Verification Testing Passed

Details

To install Tim Rayburn's GIT Aliases, run the following command from the command line or from PowerShell:

>

To upgrade Tim Rayburn's GIT Aliases, run the following command from the command line or from PowerShell:

>

To uninstall Tim Rayburn's 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 timrayburn.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 timrayburn.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 timrayburn.gitaliases installed
  win_chocolatey:
    name: timrayburn.gitaliases
    state: present
    version: 1.2.0
    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 'timrayburn.gitaliases' do
  action    :install
  version  '1.2.0'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller timrayburn.gitaliases
{
   Name     = 'timrayburn.gitaliases'
   Ensure   = 'Present'
   Version  = '1.2.0'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install timrayburn.gitaliases version="1.2.0" 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

[alias]
a = add
b = branch
c = checkout
f = fetch
l = log --pretty=oneline --abbrev-commit
r = rebase --interactive HEAD10
s = -p status
pr = pull --rebase
pom = push origin master
pos = push origin source
rc = rebase --continue
ra = rebase --abort
ss = -p status -s
lg = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative
lga = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative --all
ll = log --pretty=oneline --abbrev-commit --max-count=15
lc = log --stat --summary
tpr = tf pull --rebase --deep
tcd = tf checkin --deep
prune = fetch --prune
aliases = config --get-regexp alias
amend = commit --amend
bl = blame -w -M -C
bra = branch -rav
branches = branch -rav
changed = status -sb
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
lastref = rev-parse --short HEAD
lasttag = describe --tags --abbrev=0
pick = add -p
remotes = remote -v show
stage = add
standup = log --since yesterday --oneline --author Tim Rayburn
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 --
[color]
branch = auto
diff = auto
status = auto
[color "branch"]
current = yellow reverse
local = yellow
remote = green
[color "diff"]
meta = yellow bold
frag = magenta bold
old = red bold
new = green bold
[color "status"]
added = yellow
changed = green
untracked = cyan


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
Tim Rayburn's GIT Aliases 1.1.0 361 Monday, September 16, 2013 Unknown
Tim Rayburn's GIT Aliases 1.0.6 351 Monday, July 15, 2013 Unknown
Tim Rayburn's GIT Aliases 1.0.5 367 Monday, July 15, 2013 Unknown
Tim Rayburn's GIT Aliases 1.0.4 369 Wednesday, June 5, 2013 Unknown
Tim Rayburn's GIT Aliases 1.0.3 342 Tuesday, June 4, 2013 Unknown
Git - Aliases 1.0.2 381 Tuesday, June 4, 2013 Unknown
Git - Aliases 1.0.1 354 Tuesday, June 4, 2013 Unknown
Git - Aliases 1.0.0 334 Tuesday, June 4, 2013 Unknown
Discussion for the Tim Rayburn's GIT Aliases Package

Ground Rules:

  • This discussion is only about Tim Rayburn's GIT Aliases and the Tim Rayburn's 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 Tim Rayburn's 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