Repository navigation
feature request: resume #49
Description
Activity
My guess is that I would wind up with all the successfully imported issues duplicated if I tried to run it again, and I also don't have a straightforward way to figure out which issues were imported successfully.
For this reason I added the
--issues 25 26 29option, so you can hand-pick which issues are imported.But as you say, it's not very helpful if you still have to sand through the target repository making a list of which issues were successfully added.
Maybe, at a minimum, the script could output a progress log so that it would be easier to determine which IDs are left that need to be imported?
I thought it did. The script should output "Successfully created issue 'Made some changes'" and "Successfully created 4 comments" for every issue it creates (make sure you run the script in the terminal, and not just double-clicking the Python script).
Even better would be support for some kind of
--resumearg.I considered it while writing the script, but the reason I didn't implement any sort of
--resumefeature is because the script would need to physically store data on the computer. At the moment, everything gets stored in RAM, and doesn't affect the user's computer in any way. It's "clean" that way.Adding this feature would require a large re-write of the code.
However, the script is due for a re-write as there are a few features that need fixing at the same time.
Related to #48. When a failure occurs, there doesn't seem to be a good way to resume an import. My guess is that I would wind up with all the successfully imported issues duplicated if I tried to run it again, and I also don't have a straightforward way to figure out which issues were imported successfully.
Maybe, at a minimum, the script could output a progress log so that it would be easier to determine which IDs are left that need to be imported? Even better would be support for some kind of
--resumearg.