Willie Abrams willie

Obviously, the simplest solution would be for the client to share their account details or add us as ‘team admin’, but that is not what this is about.

On https://developer.apple.com

[Add us to your iOS Developer Program as ‘team member’.][1]
[Create a ‘Distribution Certificate’, if you haven’t got one already.][2]
[Create a ‘App Store Distribution Provisioning Profile’.][3]
[Export the ‘Distribution Certificate’ assets and send the export and password to us.][4] (For security sake, it’s a good idea to send us the password via other means than the exported certificate. E.g. by phone/SMS.)

On https://itunesconnect.apple.com

@holman got a request about our deployment system, heaven

I know it's not a high priority, but has there been any activity on open-sourcing the core Heaven gem?

There is. I've been working on extracting the non-GitHub specific parts into two gems. This first is a CLI portion called hades. The second is an HTTP API portion called heaven.

When you open source something previously used as in internal tool like Heaven, Hubot, Boxen, etc., how do you manage and hook in the parts that need to stay internal?

Normally I focus around four questions:

WARNING: If you're reading this in 2021 or later, you're likely better served by reading:

(This gist was created in 2013 and targeted the legacy GOPATH mode.)

$ ssh -A vm
$ git config --global url."[email protected]:".insteadOf "https://github.com/"

	#!/bin/sh

	hg purge -v --all
	./make.bash
	env GOOS=windows ./make.bash --no-clean
	env GOOS=windows GOARCH=386 ./make.bash --no-clean
	env GOOS=linux ./make.bash --no-clean
	env GOOS=linux GOARCH=amd64 ./make.bash --no-clean
	env GOOS=linux GOARCH=386 ./make.bash --no-clean
	env GOOS=linux GOARCH=arm ./make.bash --no-clean

	package main

	import (
	"flag"
	"log"
	"net/http"
	"os/exec"
	)

	func runner(ch chan bool, cmd string, args ...string) {

	// Taken from the commercial iOS PDF framework http://pspdfkit.com.
	// Copyright (c) 2014 Peter Steinberger, PSPDFKit GmbH. All rights reserved.
	// Licensed under MIT (http://opensource.org/licenses/MIT)
	//
	// You should only use this in debug builds. It doesn't use private API, but I wouldn't ship it.

	// PLEASE DUPE rdar://27192338 (https://openradar.appspot.com/27192338) if you would like to see this in UIKit.

	#import <objc/runtime.h>
	#import <objc/message.h>

	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

	package main

	import(
	"log"
	"net/url"
	"net/http"
	"net/http/httputil"
	)

	func main() {

	# alias to edit commit messages without using rebase interactive
	# example: git reword commithash message
	reword = "!f() {\n GIT_SEQUENCE_EDITOR=\"sed -i 1s/^pick/reword/\" GIT_EDITOR=\"printf \\\"%s\\n\\\" \\\"$2\\\" >\" git rebase -i \"$1^\";\n git push -f;\n}; f"

	# transfer all git repos from one org to another org
	gh repo list {orgname} --limit 300 --json nameWithOwner -q '.[].nameWithOwner' \| xargs -I {} gh api --method POST repos/{}/transfer -f new_owner={neworg}

	# aliases to change a git repo from private to public, and public to private using gh-cli
	alias gitpublic="gh repo edit --accept-visibility-change-consequences --visibility public"
	alias gitprivate="gh repo edit --accept-visibility-change-consequences --visibility private"