Setup remote repository:
ssh git@example.com
mkdir my_project.git
cd my_project.git
git init --bare
On local machine:
cd my_project
[user] | |
name = Pavan Kumar Sunkara | |
email = pavan.sss1991@gmail.com | |
username = pksunkara | |
[init] | |
defaultBranch = master | |
[core] | |
editor = nvim | |
whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol | |
pager = delta |
class FullPaths(argparse.Action): | |
"""Expand user- and relative-paths""" | |
def __call__(self, parser, namespace, values, option_string=None): | |
setattr(namespace, self.dest, os.path.abspath(os.path.expanduser(values))) | |
def get_args(): | |
parser = argparse.ArgumentParser(description='Something smart here') | |
parser.add_argument('my_conf', help='The configuration file for the db', action = FullPaths) | |
return parser.parse_args() |
Setup remote repository:
ssh git@example.com
mkdir my_project.git
cd my_project.git
git init --bare
On local machine:
cd my_project
#!/bin/bash | |
# bash generate random alphanumeric string | |
# | |
# bash generate random 32 character alphanumeric string (upper and lowercase) and | |
NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) | |
# bash generate random 32 character alphanumeric string (lowercase only) | |
cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 32 | head -n 1 |
curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}' |
#!/usr/bin/env python | |
from __future__ import print_function | |
import timeit | |
import numpy as np | |
from distutils.version import StrictVersion | |
from six.moves import range | |
setup = """ | |
import numpy as np | |
from six.moves import range |
git add HISTORY.md
git commit -m "Changelog for upcoming release 0.1.1."
bumpversion patch
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc
ZIP,LAT,LNG | |
00601,18.180555, -66.749961 | |
00602,18.361945, -67.175597 | |
00603,18.455183, -67.119887 | |
00606,18.158345, -66.932911 | |
00610,18.295366, -67.125135 | |
00612,18.402253, -66.711397 | |
00616,18.420412, -66.671979 | |
00617,18.445147, -66.559696 |
Mkdown renders Markdown GitHub gists with alternative CSS. Use it to elegantly share gists written in Markdown.
To create your own mkdown URL, append the gist ID in a URL of the form: http://mkdown.com/{GIST ID}
. The gist ID is the string at the end of a gist URL.