GeezerVison

What about fixing this for everyone that isn't me then?
Will something be done to fix this rate limiting issue? This PR at least proposes a generic workaround. Is it a hassle to set up? Sure
Does it solve a problem for people who are straight up blocked? Yes
Just making sure this isn't the end of the road for fixing this issue permanently

The solution implemented in this PR will continue to work exactly as today, for users not setting up til github.com PAT in their GHE project.

It will work until they hit a rate limit.

This PR provides a solution to that, for those interested. Isn't that to prefer, compared to not have a solution?

It doesn't seem like a common issue so far, but we have thought about it.

Having to add a GHES-specific input to an action suggests to me that there's a smoother flow we should look for on the backend. The solution we would like to implement is to make this flow part of GitHub Connect. That would solve the problem in a general way for all first-party actions and be consistent with other flows that fit this pattern. No ETA on this, though.

Hello @brcrista
I am working in the automation team. We do the automation in ansible. Github is used heavily in our company (Kyndryl) and we really need this fix ASAP. Could you please help me, what can we do to prioritize this issue to be fixed in very near future?

@Vercasek1985 I recommend forking the action to unblock yourself. As I said above, passing a PAT is a quick fix but not something that we want to support long-term.

@HenrikPoulsen I'm going to close this PR since we're not planning on merging it.