| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork git@github...my-fork.git |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
| Version 2, December 2004 | |
| Copyright (C) 2011 Sebastien P. https://twitter.com/#!/_sebastienp | |
| Everyone is permitted to copy and distribute verbatim or modified | |
| copies of this license document, and changing it is allowed as long | |
| as the name is changed. | |
| DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
| #!/bin/bash | |
| PERL_STABLE="5.16.1" | |
| echo '%< --- installing perlbrew ---' | |
| echo | |
| curl -kL http://install.perlbrew.pl | bash | |
| source ~/perl5/perlbrew/etc/bashrc | |
| perlbrew install --notest perl-${PERL_STABLE} |
| ############################################################################### | |
| # The MIT License | |
| # | |
| # Copyright 2012-2014 Jakub Jirutka <jakub@jirutka.cz>. | |
| # | |
| # 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 |
| #!/bin/bash | |
| # | |
| # Whitelist Pingdom probe-servers in iptables. | |
| # | |
| # Create a chain called "PINGDOM" and jump to it somewhere before | |
| # the final REJECT/DROP, e.g. | |
| # | |
| # # New chain for Pingdom rules | |
| # :PINGDOM - [0:0] | |
| # |
| ################################################################# | |
| # = This script transfers bash history to zsh history | |
| # = Change bash and zsh history files, if you don't use defaults | |
| # | |
| # = Usage: ruby bash_to_zsh_history.rb | |
| # | |
| # = Author: Ankit Goyal | |
| ################################################################# | |
| # change if you don't use default values |
| /** | |
| * World's simplest express server | |
| * - used to serve index.html from /public | |
| */ | |
| var express = require('express'); | |
| var serveStatic = require('serve-static'); | |
| var app = express(); | |
| app.use(serveStatic(__dirname + '/public')); |
| # see https://www.topbug.net/blog/2013/04/14/install-and-use-gnu-command-line-tools-in-mac-os-x/ | |
| # core | |
| brew install coreutils | |
| # key commands | |
| brew install binutils | |
| brew install diffutils | |
| brew install ed --default-names | |
| brew install findutils --with-default-names |
| #! /bin/bash | |
| if [ -z "$1" ]; then | |
| echo "please supply at least one server to connect to" >&2 | |
| exit 1 | |
| fi | |
| target=multi-ssh-$$ | |
| if [ -z "$TMUX" ]; then |
Last Updated: March 2023
IMPORTANT: Ignore the out-of-date steps below for getting Chromium keys.
Instead, read this up-to-date guide (Jan 2023) written by @LearningToPi.
P.S. Thank you to every contributor below who provided tips over the years on what should be a straightforward process: setting up Chromium for local development.
Long live the web!
