Skip to content

Instantly share code, notes, and snippets.

Bradley Davis bad884

  • Intuit
  • San Jose, California
Block or report user

Report or block bad884

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
ssh-keygen -t rsa -b 4096 -C ""
cat .ssh/
read -p "Press enter to continue after adding SSH to Github"
git clone .dotfiles
python ~/.dotfiles/.config/
source ~/.bashrc
JasonMoho /
Last active Oct 2, 2018
Ceph benchmarking scripts
for i in $(seq 0 1 9)
HEADER="########### SIZE = $SIZE ###########"
echo $HEADER >> outwdbench.txt 2>&1
for j in $(seq 0 1 4)
echo $SEP >> outwdbench.txt 2>&1
CMD="dd if=/dev/zero of=here bs=1M count=$SIZE oflag=direct"
set -eou pipefail
# From and
if [[ $(defaults -currentHost read ~/Library/Preferences/ByHost/ doNotDisturb) -eq 0 ]]; then
defaults -currentHost write ~/Library/Preferences/ByHost/ doNotDisturb -boolean true
defaults -currentHost write ~/Library/Preferences/ByHost/ doNotDisturbDate -date "`date -u +\"%Y-%m-%d %H:%M:%S +000\"`"
NeoTheFox / kitty.conf
Last active Apr 22, 2019
kitty config with solarized dark theme
View kitty.conf
# vim:fileencoding=utf-8:ft=conf
# Font family. You can also specify different fonts for the
# bold/italic/bold-italic variants. By default they are derived automatically,
# by the OSes font system. Setting them manually is useful for font families
# that have many weight variants like Book, Medium, Thick, etc. For example:
# font_family Operator Mono Book
# bold_font Operator Mono Thick
# bold_italic_font Operator Mono Medium
font_family Hack
noelbundick / LICENSE
Last active Jul 25, 2019
Solarized Dark for Bash on Windows
MIT License
Copyright (c) 2018 Noel Bundick
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
erikmchut / .inputrc
Created Mar 17, 2017
My .inputrc with both emacs + vim goodness
View .inputrc
# Use Unicode & do NOT use the "8bit hack" to input/output non-ASCII characters
set input-meta on
set output-meta on
set convert-meta off
# Ignore completion case
set completion-ignore-case On
set match-hidden-files Off
set bell-style visible
jpierson /
Last active Jun 25, 2019 — forked from jagregory/gist:710671
How to move to a fork after cloning

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

  1. Clone some repo (you've probably already done this step)

    git clone git@github...some-repo.git
pandafulmanda / Python3 Virtualenv
Last active Aug 16, 2019 — forked from akszydelko/Python3 Virtualenv
Setting up and using Python3 Virtualenv on Mac
View Python3 Virtualenv

Python3 Virtualenv Setup

  • Python 3
  • Pip 3
$ brew install python3
santisbon /
Last active Aug 15, 2019
Bring your feature branch up to date with master. Deploying from Git branches adds flexibility. Bring your branch up to date with master and deploy it to make sure everything works. If everything looks good the branch can be merged. Otherwise, you can deploy your master branch to return production to its stable state.

Updating a feature branch

First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)

$ git checkout master

Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master

You can’t perform that action at this time.