Check that new repositories don't match exisiting repositories
lazappi opened this issue · comments
When running the check command in the app "new" repositories can be incorrectly found if they are new to the local packages cached but have already been added to the database (by somebody else). The app should check that any new matches are not the same as what is currently in that tool entry before suggesting them as new repositories.
I can't seem to reproduce this and the code should be taking care of it so going to close for now. Will reopen if needed.