@oelburk Unfortunately, there’s no news on this issue yet. The team is aware, but there’s no ETA, so I can’t promise any specific timeline.
In the meantime, @lucasmotta suggested a working workaround above: create a Personal Access Token on GitHub with the needed scopes issues and pull requests, then add it to your cloud environment as a variable:
GH_TOKEN=ghp_your_token
After that, the gh CLI will use this token instead of the limited installation token. Give it a try, it helped a few users.