Closed miquelduranfrigola closed 1 month ago
Thought: this may be moved to the ersilia-stats repository, if needed.
This is linked to ersilia-os/ersilia#768
I don't think this should go to the ersilia-stats, as this is a maintenance issue not a stats issue
I agree. I am just worried that we will have too many actions in ersilia
and this may become difficult to manage/browse. We could create an ersilia-maintenance
repo for these kinds of tasks, although I am not convinced either.
Update for the upcoming Harvard T4SG round, we have suggested the creation of an ersilia-maintenance
repository.
Ok, we have an ersilia-maintenance repository now, so is this problem being tackled there already? and if not, can we transfer the issue there so that it gets in the right repo @DhanshreeA ?
This problem is not being tackled, as evidenced by us having to delete/add entries manually in Airtable. Transferring this issue to ersilia-maintenance, and assigning myself.
Currently if, for some reason, a model GitHub repository is deleted, the AirTable registry is not aware of it. Likewise, if a record is deleted from AirTable, the repository remains in GitHub.
It would be nice to develop a GitHub Action that checks coherence between available GitHub repositories and records in AirTable. At the end of the action, if any incosistency is found, we could send a message to Slack.