robandpdx

Assuming you already have an ssh key pair for each account and you are using that ssh private key to sign commits, you can manage the different accounts by configuring git to use a different configuration profile based on the directory under which you are cloing the repository.

For each key pair (account) you will create a config file that will apply to all the projects under that account's work directory.

/Users/robandpdx/
    |__.gitconfig
    |__.gitconfig.work
    |__.gitconfig.personal
    |__github-work/                # <--- This is where you will clone all your work repositories

robandpdx

Converting CircleCI workflows to GitHub Actions

Start by using GitHub Actions Importer (GAI) Follow the getting started instructions to install and configure GAI.

Run an audit with GAI

gh actions-importer audit circle-ci --output-dir audit

robandpdx

ghec-importer examples

The following example will remove the teams from the migration_archive.tar.gz file.

export GHEC_IMPORTER_ADMIN_TOKEN="xxxx"
ghec-importer prepare-archive -r teams migration_archive.tar.gz

The following example will import the migration_archive.tar.gz into the robandpdx-migaration5 org and enable actions on the repo. If there is a repo name conflict, if will be resolved by adding the source org name to the repo name as a prefix.

robandpdx

Rewriting repository history

Sometimes history rewrites are required in order to migrate repositories into github.com. Several factors can dictate the need to rewrite history of a repository:

• objects larger than 100Mb
• commits larger than the 2GB push limit

Although rewriting history might not be required for your repository to migrate to github.com, you may consider rewriting history for several reasons:

• migrate large objects to LFS
• cleanup previous mistakes or bad practices that caused repo bloat
• remove secrets from repo history

robandpdx

Running metric-server on Kind Kubernetes

Deploy latest metric-server release.

kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.5.0/components.yaml

You need to add argument --kubelet-insecure-tls to the metrics-server container.

robandpdx

Issue ops use cases

• repo creation
• request-marketplace-actions
• migration via actions
• stale repo finder
• stale repo removal
• provision something
• destroy something
• change something

robandpdx

How to get a shell on a GH runner

Getting a shell on a GH runner is pretty easy. First, create a linux VM in your favorite cloud provider. Be sure to allow inbound traffic on port 22 and 1337. SSH into that VM and execute the following command:

nc -nvlp 1337

Then run the following workflow in GH actions:

name: Reverse shell

robandpdx

These instructions explain how to migrate a repo from GitHub Enterprise Server to GitHub Enterprise Cloud using the gh gei CLI when either:

• (a) you want to use an unsupported blob storage provider; or
• (b) you want to use a supported blob storage provider with different authentication

The following instructions assume that you have curl and jq installed. There are available for Linux, macOS and Windows Subsystem for Linux (WSL).

1. Make a note of your GitHub Enterprise Server hostname (e.g. github.acmecorp.com) and expose it as the GHES_HOST environment variable: export GHES_HOST=github.acmecorp.com.
2. Make a note of the GitHub Enterprise Server organization that owns your origin repo, and expose it as the GHES_ORGANIZATION environment variable: export GHES_ORGANIZATION=engineering.
3. Make a note of the name of the repo you are migrating in GitHub Enterprise Server, and expose it as the GHES_REPO environment variable: export GHES_REPO=webapp.

robandpdx

Migration Guide from Gerrit to GitHub

Scope of the document

This document provides the steps involved in migrating source code from Gerrit to GitHub. The CI/CD setup part is currently out of scope of this document.

Introduction

Below is a guided procedure to ensure a migration from Gerrit to GitHub.

Migration steps

The following steps act as high-level phases when implementing a migration project:

robandpdx

Stacked diff workflow

ghstack

ghstack
Stacked diffs and ghstack
Ghstack is a little rough around the edges. It seems to work as advertised, but some of the ways it works are a bit quirky. The following is a list of things I don't like about ghstack:

• it creates 3 branches for each commit
• PR are from head->base rather than from branch->master
• you need force push access to main in order to land a PR
• branch protection rules are useless, need to be bypassed by force pushes