---

---

Transfer Issues by Label (Workflow)

This workflow (action) for GitHub allows you to automatically move issues to the target repository you choose.
You can assign a label to a type of issue and, when someone applies it, the issue is instantly transferred.
With this wonderfull tool, you can:

• ✅ Move security-risk issues to a private repository. (See ⇾ 💡)
• ✅ Move multiple issues at once by assigning the label you have defined. (e.g., “move”, “high”, “risk”…)
• ✅ Send spam issues or trash reports to a separate repository. (See ⇾ 💡)
• ✅ Set different target repositories for different labels. (See ⇾ 💡)
• ✅ Create a single action per transfer type or group all transfers into one workflow.
• ✅ Use it however you want — it’s extremely versatile!. 👍

▶ Try it ⇾ Send a Security Risk

---

💡 Tips

• You can create a Security Risk template and define which repository should receive those issues in the workflow.
  When someone reports a risk using that template, the issue will be instantly transferred — like magic. 🧙‍♂️

• To move issues to different repositories, create two or more workflows with different names.

• You can move multiple issues to the assigned repository in a single shot.
  
  To do this:

  1. Set the label name and the target repository in the workflow (one‑time setup).
  2. Select and assign the label to the issues you want to move (whenever you need).
  3. When the action finishes, the issues will disappear from the source repository.

• You can quickly clean a repository by recycling it (delete/create) or simply forget it exists… 🤷

• You can also create an action that periodically empties your “recycle bin” repository. 🗑️

---

Getting Started

With this workflow, you can define one or more labels that will be used to transfer issues to another repository.
The action listens for the “labeled” event and performs the transfer whenever the chosen label is applied.

Some steps are requiered to use this workflow:

1. Create an action with the content of Transfer_Issues_by_label.yml

   • Go to: Actions > New workflow > Setup a workflow yourself. Then, replace the content with the script copied.
   • Or download the script and add it to your .github/worflows foler.

2. Create a personal access token (PAT) with repository permissions. (enable all "repo" scopes)

   • Go to: User Settings > Developer settings > Personal access tokens > Generate new access token.
     
   • Then copy the token.

3. Create a secret named ACTIONSYNC and use the PAT created in the previous step.

   • Go to: Repo Settings > Secrets > New repository secret.
   • Then paste the token from step 2.
     
     ℹ The secret must be created in the source reposotory, where the action runs.
     ⚠ If you arere not the target repository owner, the owner must also create the PAT from step 2

4. Create a target repository or use an existing one

   • To use default variables, name the target repository SourceRepoName_Private
   • To use a different reopsitory, change the value of the TargetRepo variable
   • If the target will receive confidential issues (e.g, security ristks) set it as Private.

5. Adjust the variables in the action created in step 1 as nedded.

   • In most cases, you only need set LabelName to the the label that will trigger the action.
     
     ℹ By default, Variables use the owner and source repository where the action is running.
     The target repository is set to SourceOwnerUsername/SourceRepoName_Private.

   • For other scenarios, adjust any variable as needed.

Variable definitions

• LabelName - The name of the label or labels (comma-separated) that triggers the issue transfer.
• GITHUB_TOKEN - The personal access token (PAT) or repository secret containing the PAT.
• SourceOwner - The owner username of the source repository where the action runs and the issue is taken.
• SourceRepo - The source repository where the action runs and the issue is taken.
• TargetOwner - The owner username of the target repository where the issue will be sent.
• TargetRepo - The target repository where the issue will be sent.

Technical details

This workflow uses GitHub - Actions and GitHub Api - GraphQL

---

Support Development

Paypal	Github	Ko-Fi