ex-meta now at a startup, thanks for making stacke...
# how-do-i
j
ex-meta now at a startup, thanks for making stacked diffs a thing IRL! 🙂 our use case: we have a product to fix static analysis issues across a codebase automatically, we want our client to review all of them easily; right now that means creating a stack of size ~200 in one go (1 static analysis issue = 1 branch) I can
gt create
the stack no probs, but when I
gt submit
I run into "Looks like you've triggered a GitHub API secondary rate limit 🥞 Nice stack!" pretty frequently (usually can get 20ish PRs submitted every 20-30m; and after 100 ish I'm stuck for the day) Is there a way around this? (can we get increased rate limit)
d
unfortunately the rate limit is on GitHub's side
we can think of ways to improve this though!
e
you could make the pipe bigger or create a funnel for the pipe. virtualized github user accounts (make the pipe bigger) or a queue system in graphite's backend to manage the rate limited endpoint (create a funnel for the pipe). Or call up github and get an exception for the rate limit. Maybe graphite could be the conduit for that for their users.
j
@David Balatero Is there a way I can increase the rate limit on my side with GitHub? (e.g does the rate limit depend on which pricing tier I am on GH? can I email GH support?)
d
i'm not quite sure on that - you might reach out to github and ask!
j
@David Balatero So confirming: when I run
gt submit
, Graphite is making some API call w/ my GitHub account and it is my account that is being rate limited by GH? (rather than Graphite's account being rate limited)
d
yeah that's correct
i don't have deep info on this btw, rate limiting isn't something i work on closely