https://github.com/buildo/gh-issue-mover
A friendly CLI tool to migrate GitHub and GitHub Enteprise issues
https://github.com/buildo/gh-issue-mover
Last synced: about 1 year ago
JSON representation
A friendly CLI tool to migrate GitHub and GitHub Enteprise issues
- Host: GitHub
- URL: https://github.com/buildo/gh-issue-mover
- Owner: buildo
- License: mit
- Created: 2016-09-13T09:39:02.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2022-12-06T11:19:00.000Z (over 3 years ago)
- Last Synced: 2023-04-10T01:35:01.307Z (over 3 years ago)
- Language: JavaScript
- Size: 236 KB
- Stars: 7
- Watchers: 5
- Forks: 10
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://www.npmjs.com/package/gh-issue-mover)
# 🚚 gh issue mover
A friendly CLI tool to migrate issues across GitHub and GitHub Enteprise repos.
## Features
- migrate issues one by one or in bulk using labels
- include comments, labels and assignees in the migration
- include references to the original issue and author
- close the original issue with a link to a new one
- works with both (and across) GitHub and GitHub Enterprise
## Example
| original issue | migrated issue |
|:---------------:|:---------------:|
|  |  |
## Usage
Install from npm:
```sh
npm install -g gh-issue-mover
```
Then create configuration file (e.g. `config.json`) that contains two keys `fromRepo` and `toRepo`:
```json
{
"fromRepo": {
"owner": "buildo",
"name": "aliniq",
"token": "1231231231231231231231231231231231231213212312",
"rootURL": "https://github-enterprise.example.com/api/v3"
},
"toRepo": {
"owner": "buildo",
"name": "ams",
"token": "1231231231231231231231231231231231231213212312",
"rootURL": "https://github-enterprise.example.com/api/v3"
}
}
```
`owner` and `name` indentify the repos you want to migrate the issue to/from.
`token` must be a github token with read permissions on the `fromRepo` and write permissions on `toRepo`.
`rootURL` is the GitHub API endpoint (only required for GitHub Enterprise repos)
Once you have a valid `config.json`, run
```sh
gh-issue-mover --config=config.json
```
and follow the interactive prompt.