rate limit exceeded causes digger to silently fail

[motatoes]

just saw this, I think it is what alot of customers face when they say they commented digger plan but saw nothing, documenting for later

time=2025-06-02T22:02:55.877-07:00 level=ERROR msg="Error initializing comment reporter" issueNumber=3 error="count not initialize comment reporter: could not publish comment to PR 3, POST https://api.github.com/repos/diggerhq/terragrunt-huge-example/issues/3/comments: 403 API rate limit exceeded for installation ID 61306309. If you reach out to GitHub Support for help, please include the request ID ECFF:227F0B:103BFA0D:10BDC807:683E81FF and timestamp 2025-06-03 05:02:55 UTC. [rate reset in 26m28s]"

The rate limit per installation of github app is 5000 requests per hour. I'm not sure why we are reaching that limit sometimes but it could be because we comment, update comment and also attempt to fetch workflow url which could be 5-10 requests per impacted project. To be investigated

[raouf-xh]

We ran into a similar issue when installing the Digger GitHub App on a new repo and got this error screen:

Even though the Digger App was added to the repo, it wasn't working on both creating a PR and commenting digger plan. We had to reinstall the app and make sure we get a success screen for it to work: