vlsi commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207186354
> There will also be pull requests (we already heavily use it) Just in case: I'm doing the migration for Apache JMeter (see https://github.com/vlsi/bugzilla2github). >I'm just curious if there is a way to correctly determine the issue numbers while new issues/PRs are arrived during importing I do not think so. As far as I know, the issues are allocated sequentially, and the latest assigned number can be fetched via https://api.github.com/repos/apache/lucene/issues?per_page=1 API (see `number: 1058`). With JMeter, the flow of issues and PRs is not really high, so we would just make everything read-only during the migration. --- > issue numbers while new issues/PRs are arrived during importing I assume you use bulk issue import API (https://gist.github.com/jonmagic/5282384165e0f86ef105), and if you wait for the import to complete, then it does return the assigned issue_number. However, the key need for pre-assigning the numbers is that you could generate comments that reference "issues that will be created later". If GitHub breaks, you could just continue from what you stopped. On the other hand, if you really want to allow creating issues and pull requests during the migration, then you can't easily "reference non-yet-created issues" since every PR created will shift the numbers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
