# Github Issues Migration

### Preparation

You'll need to pick a particular release you want to target that will be your last plan.io release. You'll need a clean break meaning that you'll want to close all PRs pointing to plan.io issues.

You'll also want to set up Github Issues with labels, milestones, etc.

### Steps

1. After the release, close/update any open PRs linking to redmine
1. Remove your repo from the PR processor https://git.io/Jtsz5
1. Go to your project repo settings in plan.io and remove the repo.
1. Update pyproject.toml and point towncrier to github issues
1. Update the issue checker workflow to look at github issues
1. Move issues from redmine to Github Issues

### Plugin Template Changes TODO
- [x] 1. Add new config variable: issue_tracker = 'redmine' or 'github'
- [x] 2. Update [commit checker](https://github.com/pulp/plugin_template/blob/master/templates/github/.ci/scripts/validate_commit_message.py.j2) to use issue_tracker specific logic
- [x] 3. Update the [release script](https://github.com/pulp/plugin_template/blob/master/templates/github/.ci/scripts/release.py.j2) to not generate redmine querys if github is issue tracker
- [x] 4. Add logic to unset update_redmine if issue_tracker is 'github', also add print message to tell user to remove repo from Pulp-CI PR processor and remove the repo from plan.io
- [x] 5. Update pyproject.toml to point towncrier to github issues, this might need special logic since it's outside of the github templates
- [x] 6. Update [main readme](https://github.com/pulp/plugin_template/blob/master/README.md) and the [bootstrap readme](https://github.com/pulp/plugin_template/blob/master/templates/bootstrap/README.md.j2), also might need special logic since outside of github templates
- [x] 7. Maybe add special --migrate_issue_tracker command to simplify logic from previous three steps?