Gabriel Staples ElectricRCAircraftGuy

Merge Wiki Changes From A Forked Github Repo

This is inspired (or basically copied) from How To Merge Github Wiki Changes From One Repository To Another, by Roman Ivanov, and serves to ensure that should something happen to the original article, the information remains nice and safe here.

Terminology

OREPO: original repo - the repo created or maintained by the owner

FREPO: the forked repo that presumably has updates to its wiki, not yet on the OREPO

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

To create anchor links that jump down to different sections of a README (as in an interactive table of contents), first create a heading:
#Real Cool Heading

The anchor link for that heading is the lowercase heading name with dashes where there are spaces. You can always get the anchor name by visiting the README on Github.com and clicking on the anchor that appears when you hover to the left of the heading. Copy everything starting at the #:
#real-cool-heading

Wherever you want to link to your Real Cool Heading section, put your desired text in brackets, followed by the anchor link in parentheses:
[Go to Real Cool Heading section](#real-cool-heading)

There are two types of markup in Liquid: Output and Tag.

Output markup (which may resolve to text) is surrounded by

{{ matched pairs of curly brackets (ie, braces) }}

Tag markup (which cannot resolve to text) is surrounded by

	#include <utility>
	#include <functional>
	#include <type_traits>
	#include <typeinfo>

	#include <iostream>

	namespace meta {

	// detects callable objects, not functions

	(function () {
	'use strict';

	var body = document.body,
	html = document.documentElement;

	var docHeight = Math.max(body.scrollHeight, body.offsetHeight, html.clientHeight, html.scrollHeight, html.offsetHeight);

	var findingColor = 'limegreen';

	#!/bin/sh

	# inspired by this SO answer by Uwe Geuder
	# http://stackoverflow.com/questions/277546/can-i-use-git-to-search-for-matching-filenames-in-a-repository/6960138#6960138
	# this will create one 'foundin-$rev.txt' file for each of your revisions, feel free to delete them after use

	# ADJUST THIS TO YOUR NEEDS:
	SEARCHTERM="file-that-was-long-lost.txt"

	To find your public SSH key(s) on github, navigate to:
	https://github.com/<username>.keys

	ssh-keygen
	-t ed25519 - for greatest security (bits are a fixed size and -b flag will be ignored)
	-t rsa - for greatest portability (key needs to be greater than 4096 bits)
	-t ecdsa - faster than RSA or DSA (bits can only be 256, 284, or 521)
	-t dsa - DEEMED INSECURE - DSA limted to 1024 bit key as specified by FIPS 186-2, No longer allowed by default in OpenSSH 7.0+
	-t rsa1 - DEEMED INSECURE - has weaknesses and shouldn't be used (used in protocol 1)

	To use: create a new bookmark and paste into the URL field.

	In Chrome, you can paste the full multiline code as shown below.
	In other browsers, you may need to minify the code into one line first.

	javascript:
	document.querySelectorAll('.load-diff-button').forEach(node => node.click())