Gregor Martynus

I'm glad you are unblocked for now. I don't want to merge the current changes, I'd like to do some more research. I think the current changes patch over the...

> but I'm getting a 422 response That usually means you don't have the permission. What we fixed was the permissions setting, they actually work now. Before the recent changes,...

> However if we remove permission-* setting(so token inherits all permissions), then it works again. This also supports my assumption above. To make it work again, remove all `permission-*` settings....

Can you share 1. Permissions of your installations 2. The workflow file that uses `actions/create-github-app-token`, or at least the step where you set the permissions?

Sorry, we didn't get to this in time. Please re-create the PR if the change is still needed and we'll take a look! This comment is automated as part of...

JWTs are very short lived, app.js relies on being able to create one as needed for it to function. What do you need to use the JWT for? You can...

We are looking into it, one thing we want to make sure is that the options look the same across providers. Thank you for the great PR!

Hmm interesting bug 😁 These files are generated, we do not write any of them manually. They are based on the files at https://github.com/github/rest-api-description, could you please file an issue...

That is odd, the fact that the bearer token (JSON Web Token) was generated suggests that the action did receive an app ID and a private key, but that the...

Hi there, I see `gh pr edit` started to fail once 4 days ago, and continuously 2 days ago. It's open source so you can see the workflow and action...