anthony-telljohann

#! /usr/bin/env bash

function git.delete_merged_and_stale_branches() {
  BRANCH_WHITELIST="(\*|master|other-special-branches)" # Add more branches here as pipe-separated list
  REMOTES="origin"                                      # Add more remotes here as space-separated list
  DAYS_TO_WAIT_BEFORE_DELETING="7"
  for remote in $REMOTES; do
    echo "deleting merged branches from $remote"
    git fetch "$remote" --prune
    for branch in $(git branch -r --merged |

anthony-telljohann

Keybase proof

I hereby claim:

• I am anthony-telljohann on github.
• I am anthonytelljohan (https://keybase.io/anthonytelljohan) on keybase.
• I have a public key whose fingerprint is 8C95 B2FB 62CB CBE0 F032 23F5 A2D6 5680 7B91 DAD1

To claim this, I am signing this object:

anthony-telljohann

alias updateOS='sudo softwareupdate -i -a --restart'
alias updateHomebrew='brew update; brew upgrade; brew cleanup'
alias updateCasks='brew cask upgrade --greedy'
alias updateNVM='nvm install node; nvm use node'
alias updateNPM='npm install npm -g; npm update -g'
alias updateYarn='yarn global upgrade --latest'
alias update='updateOS; updateHomebrew; updateCasks; updateNVM; updateNPM; updateYarn'

anthony-telljohann

#!/usr/bin/env bash
# 
# Bootstrap script for setting up a new OSX machine
# 
# This should be idempotent so it can be run multiple times.
#
# Some apps don't have a cask and so still need to be installed by hand. These
# include:
#
# - Twitter (app store)

anthony-telljohann

I think we have a misunderstanding. I'll try my best to provide clarity by sharing our values and our concerns.

Regarding quality software, we believe

• Code should be consistent.
• Code should be clear.

Regarding consistency

I agree we should have consistency in our code. However, we do not enforce consistency. Instead, we are enforcing semicolons at the end of every statement. Considering semicolon usage is one of hundreds of rules to enforce code consistency, I disagree removing it will lead to inconsistency between code bases. We already have inconsistency.

Considering we desire code consistency, I propose we have a conversation regarding enforcing consistency. However, I believe that is outside of scope regarding semicolon usage.

anthony-telljohann

> cross-env NODE_ENV=test nyc mocha test/unit/**/*.js



  add
    √ should be a function
    √ should return a promise
    √ should resolve a number

anthony-telljohann

#  ---------------------------------------------------------------------------
#
#  Description:  This file holds all my BASH configurations and aliases
#
#  Sections:
#  1.   Environment Configuration
#  2.   Make Terminal Better (remapping defaults and adding functionality)
#  3.   File and Folder Management
#  4.   Searching
#  5.   Process Management