github-issues-import
github-issues-import copied to clipboard
Python script to import issues from one repository into another, either one at a time or all of them at once.
After tweaking the `config.ini` like so: ``` [login] username = brainstorm password = somepwd [source] repository = INCF/biostar-central [target] repository = ialbert/biostar-central ``` I am getting the following traceback: ```...
The problem I'm trying to solve is that an issue `closed` in the source repository it will be imported as `open` in the target repository. The problem was discussed already...
Alas, issues aren't as simple as having an `open` flag. Instead, there is an Events list for an issue which determines all this: http://developer.github.com/v3/issues/events/ Those notices should be added as...
Python 2
Could you support Python 2? Even the latest yet-unreleased version of OS X doesn't come with python3.
I have encountered an strange behavior in github-issues-import when transferring an issue with many comments. If the issue in the source repository has >30 comments, only the first 30 comments...
I had an issue with a typographic quote in the title, got: ``` Traceback (most recent call last): File "gh-issues-import.py", line 387, in import_issues(issues) File "gh-issues-import.py", line 356, in import_issues...
I added this code because when I tried to migrate issues the script stopped running after github refused a connection. Only a third of the issues were migrated and it...
When I move an issue, I typically want to close the issue in the old repository.
It would be great to have a feature to add assignee for issue when porting to target repo if assignees have been already added as collaborators in target repo.
There is no way to specify an issue ID when creating a new issue, so unless precautions are taken, new issues will have a different id than the ones they...