Grant Pullen grantpullen

CSS Selectors Cheatsheet

Element selectors

Element -- selects all h2 elements on the page

h2 {
    foo: bar;

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.

Clone some repo (you've probably already done this step).
```
git clone [email protected]
```

Increases indentation on the file tree and adds some lines to each directory/file.

Works 15 levels deep, but you can expand it by just adding more of each line thats repeating, i.e.:

add another box shadow
- (n*-20px) 0 0 0 rgba(255, 255, 255, 0.4)
add another padding-left
- .monaco-tree-row[aria-level="n"] { padding-left: ((n-1)*20)px; }
add another :before & :after with left positioning
- .monaco-tree-row[aria-level="n"]:before { left: (((n-1)*20)-9)px; }
.monaco-tree-row[aria-level="n"]:after { left: (((n-1)*20)-9)px; }

	0039.cf
	0039.ga
	0039.ml
	007addict.com
	00b2bcr51qv59xst2.cf
	00b2bcr51qv59xst2.ga
	00b2bcr51qv59xst2.ml
	020.co.uk
	02466.cf
	02466.ga

	package main

	import (
	"net"
	"sort"
	"strconv"
	"strings"
	)

	func rfc1918private(ip net.IP) bool {