stefanbuck

// SYSTEM ROLE: You are "The Archive," a high-fidelity business simulation engine. // OBJECTIVE: Test if the user possesses "Founder Intuition" by comparing their choices to historical reality.

THE RULES OF ENGAGEMENT

GOAL: The user must navigate the critical first year of a legendary startup. WIN CONDITION: Survive 3 major historical crises by making decisions that align with (or outperform) the actual history. SCORING: Track "Intuition Score." Start at 0. Award +1 for matching history. Award 0 for surviving but diverging. Award -1 for a company-killing mistake.

THE GAME LOOP

stefanbuck

Octoherd script to help with the recent CircleCI’s security breach by removing deploy keys from your repos.

No warranty, use at your own risk!

Dry-run

Run the script on a single repo first. Octoherd will prompt to confim the deletion request.

stefanbuck

const alphabet = 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ';
const input = [
    "I really",
    "ScriptJava",
    ["and I", "an it's"],
    {
        m1: "love",
        m2: "!namuh retteb a"
    },

stefanbuck

#!/bin/bash --noprofile --norc -e -o pipefail {0}

stefanbuck

Max
Buddy
Charlie

stefanbuck

#!/usr/bin/env bash
#
# Authors:
#   Stefan Buck (https://github.com/stefanbuck)
#   Thomas Ruoff (https://github.com/tomru)
#
#
# Description:
#   Are you still prefixing your commits with a ticket number manually? You will love this script!
#   This is a git hook script that will automatically prefix your commit messages with a ticket

stefanbuck

#!/usr/bin/env ruby

require 'open-uri'
require 'pathname'
require 'json'

def strip_hash(f)
  ext = f.extname

  if ext.include?("?")

stefanbuck

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

stefanbuck

#!/usr/bin/env bash

IMAGE_NAME=$1

# Grep container id
CONTAINER_ID=$(docker ps -qf "name=$IMAGE_NAME")

if [ "$CONTAINER_ID" ] ; then
    # Get the health status 
    STATUS=$(docker inspect --format='{{json .State.Health.Status}}' $CONTAINER_ID);

stefanbuck

<project>
  <actions/>
  <description/>
  <keepDependencies>false</keepDependencies>
  <properties>
    <com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty plugin="build-failure-analyzer@1.19.0">
      <doNotScan>false</doNotScan>
    </com.sonyericsson.jenkins.plugins.bfa.model.ScannerJobProperty>
    <com.chikli.hudson.plugin.naginator.NaginatorOptOutProperty plugin="naginator@1.17.2">
      <optOut>false</optOut>