action-transfer-issues

Transfer issues from one repo to another, even across orgs.

Features

Transferring an issue to another repository describes GitHub’s built-in issue transfer functionality. The table below contrasts built-in transfers with this action’s transfers:

Transfers	Built-in	This Action
Between repos in the same org	🟡 Supported, without labels	🟢 Supported
Between repos in different orgs	🔴 Not Supported	🟡 Supported, without comments
Between public repos	🟡 Supported, without labels	🟢 Supported
Between private repos	🟡 Supported, without labels	🟢 Supported
From a public repo to a private repo	🟡 Supported, without labels	🟢 Supported
From a private repo to a public repo	🔴 Not Supported	🟡 Supported, without comments

Usage

Inputs

source

Required The full name of the repo (with owner) which contains issues to transfer. For example, source: smockle-archive/sandbox.

destination

Required The full name of the repo (with owner) to which issues will be transferred. For example, destination: smockle/action-transfer-issues.

issue_numbers

Required A space-delimited list of issue numbers indicating the issues to transfer. For example, issue_numbers: "1 2 3".

Environment Variables

GH_TOKEN

Required A GitHub token with the public_repo (for use in public repos) or repo (for use in private repos) scope.

Example workflow

name: Transfer issues
on: workflow_dispatch

jobs:
  transfer_issues:
    name: Transfer issues
    runs-on: ubuntu-latest
    steps:
      - uses: smockle/action-transfer-issues@dist
        with:
          source: smockle-archive/sandbox
          destination: smockle/action-transfer-issues
          issue_numbers: "1"
        env:
          GH_TOKEN: ${{ secrets.GH_TOKEN }}

Development

Publishing

After every commit to main, the “Publish” workflow uses smockle/action-release-branch to build and deploy to the dist branch (which, as noted in Example usage above, is the branch users should specify in their workflows: uses: smockle/action-transfer-issues@dist).