MoOx

// go on you labels pages
// eg https://github.com/cssnext/cssnext/labels
// paste this script in your console
// copy the output and now you can import it using https://github.com/popomore/github-labels !

var labels = [];
[].slice.call(document.querySelectorAll(".label-link"))
.forEach(function(element) {
  labels.push({
    name: element.textContent.trim(),

benjamincharity

export function PhoneInputDirective(
    $filter, $browser, $timeout
) {
    'ngInject';

    const directive = {
        restrict: 'A',
        scope: {
            phoneInput: '=',
        },

adamreisnz

Setup GitHub issue labels script

wesbos

320
321
322
323
324
325
326
327
328
329

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here

macbookandrew

/**
 * List unique CSS properties for all DOM elements
 * Initially created to list unique font stacks on a page
 * @see {@link http://stackoverflow.com/a/35022690/ Inspired by this StackOverflow answer}
 *
 * @see {@link https://gist.github.com/macbookandrew/f33dbbc0aa582d0515919dc5fb95c00a/ URL for this file}
 *
 * @author AndrewRMinion Design (https://andrewrminion.com)
 * @version 1.1
 *

sdkks

on run {input, parameters}
	-- If run without input, open random file at $HOME
	try
		set filename to POSIX path of input
	on error
		set filename to "nvim-" & (do shell script "date +%F") & "__" & (random number from 1000 to 9999) & ".txt"
	end try
	-- Set your editor here
	set myEditor to "/usr/local/bin/nvim"
	-- Open the file and auto exit after done

larsxschneider

Installation

Make a new bookmark in your browser. Set the name to Close all PR files (or something else you like) and set the URL to:

javascript:void((function(d){d.querySelectorAll('div:not(.Details--on) > div.file-header > div.file-actions > button').forEach(function(x){x.click()});})(document));

Usage