Ticket numbers are not guaranteed to correspond #8
Description
There is no way to assign a github ticket number directly when importing. Numbers are assign incrementally
This means if you start with an empty github repo, and start migrating SF across, the numbers should be 1:1
However, this is not guaranteed. If there is a silent problem migrating SF ticket n, then the script will carry on with n+1, meaning that SF(n+1) = GH(n). this can happen if SF tickets are deleted (note: distinct from closed)
We try and prevent about this by failing fast: if a curl fails, we wait and try again. If it still fails, the program exits. The user can continue execution using the -i N flag to start from SF ticket N
However, there are cases where the curl succeeds (e.g. the deleted ticket case, possibly others) but the insertion fails. These are not checked. Would require checking the json payload inspecting the URL in there and issuing another call.