moos

// per https://docs.npmjs.com/misc/scripts, npm exposes a bunch of variables to
// the environment prefixed with npm_config_*, npm_package_* and npm_lifecycle_*.
// Here's a list of all variables exposed in my setup.

npm_config_access=
npm_config_allow_same_version=
npm_config_also=
npm_config_always_auth=
npm_config_argv='{"remain":[],"cooked":["run","foo"],"original":["run","foo"]}'
npm_config_auth_type=legacy

Tiberriver256

function Get-DirectoryContent {

<#
    .SYNOPSIS
     
        Function to get directory content
    .EXAMPLE
     
        Get-DirectoryContent -Path "C:\" -HeaderName "poshserver.net" -RequestURL "http://poshserver.net" -SubfolderName "/"
		

iffy

node_modules
dist/
yarn.lock
wwwroot

bendisposto

(ns bsp.core
  (:require [clojure.repl :refer :all]
            [clojure.spec :as spec]
            [clojure.test.check :refer [quick-check]]
            [clojure.test.check.generators :as gen]
            [clojure.test.check.properties :refer [for-all]]
            [clojure.test :refer [is are run-tests deftest]]))


(defn ultrasort [coll] (seq (into (sorted-set) coll)))

espaciomore

#!/bin/bash
ARGS="${@}"
clear; 
while(true); do 
  OUTPUT=`$ARGS`
  clear 
  echo -e "${OUTPUT[@]}"
done

razbomi

'use strict';

var gulp = require('gulp');
var through = require('through2');

// https://gulp.readme.io/docs
gulp.task('default', () => {
  gulp.src('src/**/*')
      .pipe(pipeFunction())
      .pipe(gulp.dest('dist'))

noahcoad

# convert yaml to json
# pip3 install pyyaml
# http://pyyaml.org/wiki/PyYAMLDocumentation
# py3 yaml2json.py < ~/code/manpow/homeland/heartland/puphpet/config.yaml
# gist https://gist.github.com/noahcoad/51934724e0896184a2340217b383af73

import yaml, json, sys
sys.stdout.write(json.dumps(yaml.load(sys.stdin), sort_keys=True, indent=2))

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

solidnerd

Settting up a Container Registry with docker-gitlab

This should be used for new users to getting started with the container registry feature on docker-gitlab.

Requirements

• Docker Distribution >= 2.4

• Docker GitLab >= 8.8.4 ( #708 must be merged)

• TLS certificates because it should be run with https it's not designed to use it without https

yuki-takei

[
    {
        "key": "ctrl+d",
        "command": "editor.action.cutLines",
        "when": "editorTextFocus"
    },
    {
        "key": "ctrl+o",
        "command": "workbench.action.gotoSymbol"
    },