Skip to content

Instantly share code, notes, and snippets.

@devinschumacher
Last active September 13, 2024 16:54
Show Gist options
  • Save devinschumacher/d5fdf0edf2719f000e6f52e807ec928f to your computer and use it in GitHub Desktop.
Save devinschumacher/d5fdf0edf2719f000e6f52e807ec928f to your computer and use it in GitHub Desktop.
Bulk Transfer Github Issues to Another Repository
title tags image
How to Bulk Transfer Github Issues to Another Repository
git
github
programming
how to

How to Bulk Transfer Github Issues to Another Repository

Watch the video

Click to watch the video 👆



Here’s a simple command you can run in your terminal to transfer all the issues from one Github repository to another!

Pre-requisites:

  1. Make sure you have Github CLI installed:

$ brew install gh - (Mac)

  1. Make sure you are “authenticated” through Github CLI:

$ gh auth login

  1. Make sure that the repository you’re transferring from & to have the same labels, fields, etc.

NOTE: I didn't actually test step #3 above... maybe it's not a problem.

Just test it first if you're worried and LMK in the comments if it matters!

Now you’re ready to bulk transfer your issues!

Bulk Transfer your Issues CLI

  1. Open your terminal & run the command below

Just make sure to replace the `organization/repository` name syntax with the ones that you want.

In my example, those are:

  • devinschumacher/repository-a
  • devinschumacher/repository-b -R devinschumacher/repository-a
gh issue list -s all -L 500 --json number -R devinschumacher/repository-a | \
    jq -r '.[] | .number' | \
    while read issue; do
        gh issue transfer "$issue" devinschumacher/repository-b -R devinschumacher/repository-a
        sleep 3
    done

Note: Adjust the sleep <number> number at your own risk. I started without sleep and have seen account rate limits so far with 0 wait, 1 second, and even 2 seconds. It only happened once on 2 seconds but the repo had 80+ issues. So now i've changed it to 3.

Note:

  • "repository-a" is the source repository - aka where you want to transfer (move) your issues FROM
  • "repository-b" is the destination repository - aka where you want to transfer (move) your issues TO

It does not COPY them it moves them.

Bulk transfer only the ACTIVE issues (skip the closed/archived ones)

gh issue list -s open -L 500 --json number -R devinschumacher/repository-a | \
    jq -r '.[] | .number' | \
    while read issue; do
        gh issue transfer "$issue" devinschumacher/repository-b -R devinschumacher/repository-a
        sleep 3
    done
@devinschumacher
Copy link
Author

Subscribe for more awesome stuff! - https://serp.ly/@devin/email

@gxjansen
Copy link

gxjansen commented Aug 8, 2024

This worked nicely for me, thx!

Good to know for others:

  • repository-a is the source, repository-b the destiny
  • this script will not just copy, but also remove the issues from the source.

@devinschumacher
Copy link
Author

This worked nicely for me, thx!

Good to know for others:

  • repository-a is the source, repository-b the destiny
  • this script will not just copy, but also remove the issues from the source.

yes that correct. i should update the verbiage to say "move" instead of copy. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment