Open asbates opened 1 year ago
I guess we need to distinguish the case when a warning should be thrown (i.e. because there's a typo in a staged.dep file and a repo is not found) and when it shouldn't be because someone doesn't have access to something. Not sure how to do that...
Maybe a try/catch and search for something like 'cannot access'? Although that doesn't feel very robust to me.
But if there's a typo you also get access denied:
For private repositories like
chevron
, it would be nice ifdepencency_table
didn't throw warnings if the user doesn't have access. This is confusing for external collaborators, especially if someone doesn't even knowchevron
exists. I don't have an explicit suggestion unfortunately but it is off putting and suggests something is wrong even when it is not.Created on 2022-10-27 by the reprex package (v2.0.1)