Mislav Marohnić

> For now, a generated GITHUB_TOKEN is not allowed to mark a PR as ready to review **Update:** the above has now changed on the platform and doing `gh pr...

@martinvonz I'm not sure if `gh pr merge --auto` will work with GITHUB_TOKEN generated in Actions. That operation (enabling auto-merge) is completely separate from what we were discussing in this...

Thanks all for your feedback. In the latest release we replaced the "base repository" prompt with a dedicated command `gh repo set-default` which should be clearer. Please leave your feedback...

@ilovejs Please try gh v2.21.2

Fixed in https://github.com/rbenv/ruby-build/pull/2052

@hsbt Since our openssl patch only affects building `openssl-1.1.1q`, I'd vote for keeping it in code for a while still. This is to keep compatibility with custom build formula that...

Update: since https://github.com/rbenv/ruby-build/pull/2088, none of our built-in Ruby definitions link to `openssl-1.1.1q`, therefore the installation process is no longer dependent on `patch` being present on the system.

I have successfully reproduced this in GitHub CLI based on a user report https://github.com/cli/cli/issues/7283, but have been pulling my hair for one whole day while trying to come up with...

@danieljoos I've been able to reproduce this on both Windows 10 and Windows 11. To most reliably reproduce, you can try compiling `cli/cli` from source (via `script\build`), logging in via...

@danieljoos Thanks so much for diving into this. I was also looking at that Go issue, but it seemed that since that issue was opened, [changes landed to Go](https://go-review.googlesource.com/c/go/+/198043) that...