Hi @badcel I’m replying based on your @ notice here: Dependency graph manifest files limit - #52 by badcel
I’m not super familiar with our mobile apps technically (though I do use our Android app every day) but for the relation to the increased manifest file, I highly doubt they’re related. Though I can appreciate why it might come up, as you’ve noticed that the behavior is limited to one repo, and not others, and the increased limit is only on the problematic repo.
You’ve suggested that simply browsing around the repo in the iOS app is triggering this message, though I’m curious, are you (or other members of your Org) running any kind of script against that repo?
Secondary rate limits are typically nothing we have direct control over, though we do have our guide here for best practices for integrators of our API:
Though from what you’ve suggested, nothing like that is happening?
However to reiterate, I believe this would likely be unrelated to the increased manifest file limit. Unless some API action is happening to programmatically add files, triggering the secondary rate limits.