Option to throttle the action about actions-label-merge-conflict

[eps1lon]

I suspect that's very hard to do since that would introduce statefulnes into the action. Have you checked if there are existing patterns that can throttle entire runs instead if single actions?

[bryangingechen]

I hadn't. I might be misunderstanding your suggestion, but our workflow only runs this one action once every 15 minutes (and we're even using a GitHub token from an account dedicated to this workflow, so that our other workflows don't contribute to the API limit).

What sort of thing did you have in mind?

[eps1lon]

If you already throttle the action what would be achieved if the action itself throttles? I don't see how the action could throttle that couldn't be achieved at the workflow level.

The only implementation I can see for throttling at the action level would involve adding statefulness i.e. each action call needs to be aware of the previous calls. I wouldn't know where to begin with implementations. If you have a concrete implementation in form of a PR I can take a look.

[bryangingechen]

Hmm, perhaps I wasn't being clear. What I had in mind was more along the lines of adding a (user-specified?) pause after each iteration of this for loop. That way the GitHub API calls can be spread out and we can hopefully avoid getting rate limited.