Discover gists

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Managing plugins in Vim: The basics

Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo. First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).

Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default). For example, if the layout of a plugin foo is as follows:

foo/autoload/foo.vim
foo/plugin/foo.vim

Showing multiline code or JSON in the middle column of slatedocs/slate API Documentation

Slate comes with 3 built in aside class (i.e. notice, warning and success) for showing blocked notes.

Let's a new aside class pre, that will show preformatted code in the middle column.

At the end of source/stylesheets/screen.css.scss, add the following lines:

// Style an aside like  to show code in middle column

	const { execute, introspectionQuery, parse } = require('graphql');
	const { schema } = require('../index');

	describe('graphql', () => {
	describe('index', () => {
	describe('schema', () => {
	it('should be a an object', () => {
	expect(typeof schema).toBe('object');
	});

	#
	# Installs git 1.7.10 on Ubuntu 12.04 (Precise) using packages from
	# the upcoming 12.10 (Quantal) release. Should work for i386 and amd64.
	#
	# Adapted from http://pastebin.com/TXeMw1CY
	#

	HOST_ARCH=`dpkg-architecture -qDEB_HOST_ARCH_CPU`

	wget http://mirrors.us.kernel.org/ubuntu/pool/main/g/git/git_1.7.10.4-1ubuntu1_${HOST_ARCH}.deb \

	<?php

	use Doctrine\ORM\Query\SqlWalker;

	/**
	* Quick hack to allow adding a USE INDEX on the query
	*/
	class UseIndexWalker extends SqlWalker
	{
	const HINT_USE_INDEX = 'UseIndexWalker.UseIndex';

	var pubsub = {};
	(function(q) {
	var topics = {}, subUid = -1;
	q.subscribe = function(topic, func) {
	if (!topics[topic]) {
	topics[topic] = [];
	}
	var token = (++subUid).toString();
	topics[topic].push({
	token: token,

	#!/bin/bash

	# ----------------------------------------------------
	# A Shell script to take MySql database backup
	# and upload to MEGA cloud storage using megatools
	# ----------------------------------------------------
	# REQUIREMENTS : You should have -
	# 1. Registered and verified MEGA account - https://mega.nz/
	# 2. Installed megatools - https://github.com/megous/megatools
	# ----------------------------------------------------

	sudo apachectl stop
	sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist 2>/dev/null

	# browser_logging.rb will print out the browser log from Chrome
	# when running specs with "js: true". This is so we can easily debug
	# issues where there are JS errors or other console warnings/error(s), etc.
	#
	# Output file is: Rails.root/log/browser.log
	#
	# Note: Nothing will be printed out for non-JS examples.
	RSpec.configure do \|config\|
	browser_log = File.new(Rails.root.join("log/browser.log").to_s, "w")
	browser_log.sync = true