Erik wisererik

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

	package main

	import (
	"fmt"
	"reflect"
	)

	//function types
	type mapf func(interface{}) interface{}

	from sqlalchemy import create_engine
	from sqlalchemy.orm import Session
	from myapp.models import BaseModel
	import pytest


	@pytest.fixture(scope='session')
	def engine():
	return create_engine('postgresql://localhost/test_database)

	#!/usr/bin/env bash
	# This is a modification from https://gist.github.com/omegahm/28d87a4e1411c030aa89
	# Colours and convention picked from https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/


	## Instructions
	# Bash 4+ is needed because of associative arrays
	# jq (https://stedolan.github.io/jq/)
	# Create access Token from Github (https://help.github.com/articles/creating-an-access-token-for-command-line-use/) and save it under ".token" file
	# Comment / Uncomment / Add, all the labels you want