Open Keyrxng opened 1 month ago
If github issue which exists in devpool is transferred from one repo to another then:
node_id
(from the old repo) will be closednode_id
I think it sounds reasonable although not 100% accurate in terms of devpool statistics.
So it seems that when an issue is transferred to another repository or organization that the issue takes on a new
node_id
so we must update our logic to handle out-of-sync labels.We should also aim to remove any partner issues that have been deleted (I assume) but still exist within the devpool as they can belong to repos that have been deleted.
Since we already have the
IssueRemover
class we can borrow it and delete any erroneous tasks before we perform any state changes.I think we should also delete any devpool issues that's body does not match the typical url formatting standard.