isaacs

echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh

jagregory

So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear!

Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy.

* Off the top of my head *

1. Fork their repo on Github
2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it

    git remote add my-fork git@github...my-fork.git

mitchellhislop

* @property CI_DB_active_record $db
   * @property CI_DB_forge $dbforge
   * @property CI_Benchmark $benchmark
   * @property CI_Calendar $calendar
   * @property CI_Cart $cart
   * @property CI_Config $config
   * @property CI_Controller $controller
   * @property CI_Email $email
   * @property CI_Encrypt $encrypt
   * @property CI_Exceptions $exceptions

ProLoser

<h1>Alert</h1>
<p>Bootstrap JS</p>
<div class="alert fade in">
  <button type="button" class="close" data-dismiss="alert">×</button>
  <strong>Holy guacamole!</strong> Best check yo self, you're not looking too good.
</div>

<p></p><a ng-click="alert=true">Open Alert (AngularJS)</a></p>
<div class="alert fade" ng-class="{in:alert}">
  <button type="button" class="close" ng-click="alert=false">×</button>

bradical

<system-workflow-definition name="test" initial-step="initialize" >
  <triggers>
    <trigger name="email" class="com.cms.workflow.function.EmailProvider" />
    <trigger name="publish" class="com.cms.workflow.function.Publisher" />
    <trigger name="merge" class="com.cms.workflow.function.Merge" />
    <trigger name="assignStepIfUser" class="com.cms.workflow.function.AssignStepIfUser" />
    <trigger name="assignToGroupOwningAsset" class="com.cms.workflow.function.AssignToGroupOwningAsset" />
    <trigger name="assignToWorkflowOwner" class="com.cms.workflow.function.AssignToWorkflowOwner" />
    <trigger name="delete" class="com.cms.workflow.function.Delete" />
    <trigger name="deleteAndUnpublish" class="com.cms.workflow.function.DeleteAndUnpublish" />

JoelBesada

This is an example command for Backtick. A Backtick command consists of some executable JavaScript and a bit of metadata in JSON.

Here are the required steps to create a command:

1. Create a new Gist with a command.js and command.json file, or simply fork this one.

2. Write your JavaScript in command.js. This will be injected into and executed on the page the user is currently on when they run it.

3. Add some metadata to the command.json file:

• name: The name of the command.

TheHippo

OUT := binariy-name
PKG := gitlab.com/group/project
VERSION := $(shell git describe --always --long --dirty)
PKG_LIST := $(shell go list ${PKG}/... | grep -v /vendor/)
GO_FILES := $(shell find . -name '*.go' | grep -v /vendor/)

all: run

server:
	go build -i -v -o ${OUT} -ldflags="-X main.version=${VERSION}" ${PKG}

stevez

var assert = require("chai").assert;
var TennisGame = require("../src/TennisGame");


describe('Tennis Score', function() {
    
     var tests = [
      [0, 0, "Love-All"],
      [1, 1, "Fifteen-All"],
      [2, 2, "Thirty-All"],

turtlemonvh

# Borrowed from: 
# https://github.com/silven/go-example/blob/master/Makefile
# https://vic.demuzere.be/articles/golang-makefile-crosscompile/

BINARY = superdo
VET_REPORT = vet.report
TEST_REPORT = tests.xml
GOARCH = amd64

VERSION?=?

AriaFallah

#!/usr/bin/env bash

KEYCHAIN="secrets.keychain"

main () {
  if [[ -z "$1" ]]; then
    print_usage
  fi

  case "$1" in