dry-run features would be nice

[GoogleCodeExporter]

It would be nice to know what could go wrong before doing the import and ending 
up with a half-way result. Here's some of the things I would have liked, in my 
experience trying out the GitHubIssueImporter tool.

I wanted to provide a username mapping, to keep as much of the information as 
possible, but it wasn't possible to know which mappings were even needed before 
starting? I modified the script to raise an exception in _GetIssueAssignee when 
a mapping is not found, instead of returning the --github_owner_username, 
adding entries to the mapping files as errors were found.

Issues can only be assigned to users that have commit access to the repository. 
If there was a dry-run mode, it would be nice if it could check whether that's 
the case, or at least, list the users that will be needed, so it can be 
verified that they have commit access ahead of time.

Original issue reported on code.google.com by pphaneuf@google.com on 23 Aug 2014 at 2:00

[GoogleCodeExporter]

Original comment by chrsm...@google.com on 14 Mar 2015 at 10:57

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by chrsm...@google.com on 16 Mar 2015 at 1:31

• Added labels: Priority-Low
• Removed labels: Priority-Medium