When running bicho on the second GitHub repository, it only considers ticket number to decide if it is already in the database or not. This leads to different tickets to be considered as the same, and therefore, many new tickets are not inserted in the database.
To reproduce this bug, just run Bicho on two projects (repositories), and observe how the ticket numbers that are present in both, are not included for the second one.
When running bicho on the second GitHub repository, it only considers ticket number to decide if it is already in the database or not. This leads to different tickets to be considered as the same, and therefore, many new tickets are not inserted in the database. To reproduce this bug, just run Bicho on two projects (repositories), and observe how the ticket numbers that are present in both, are not included for the second one.