Hello Hiroshi, Sorry this mail is late. Many thanks for changing the settings, this works very well now! Regards, Martin. On 2026-07-27 11:30, SHIBATA Hiroshi wrote:
I have turned off the automatic Copilot review on the ruby repository. If you still want a review from Copilot on a specific pull request, you can get one by assigning Copilot as a reviewer.
Note that this does not cover every case. A review can still be requested depending on the contributor's own Copilot configuration, or on the settings of the organization that provides them with Copilot.
We cannot control either of those from the ruby org side. There are also reports of reviews firing even when everything is turned off, so a problem on the GitHub side is possible.
Also, once Copilot is assigned as a reviewer, there is no setting to suppress the comment it posts. This includes comments stating it has nothing to add or that the quota has been reached. Please filter those emails on your side. If you want this changed, the request needs to go to GitHub, so please send them your feedback directly.
On Sun, Jul 26, 2026 at 9:29 AM Martin J. Dürst via ruby-core < ruby-core@ml.ruby-lang.org> wrote:
The amount of mail I get as a Ruby committer is already significant, but lately, it has been getting worse. Copilot is producing additional mails. And most of them are useless:
1) There are the regurgitating mails. See the comment from Earlopain below for why we don't need these.
2) There are the mails that say it has no comment. No actual committer sends such mails.
3) There are the mails that say that it "was unable to review this pull request because the user who requested the review has reached their quota limit.". No actual committer sends out mails e.g. saying they are currently busy with their day job.
Can we change the settings so that such emails are not sent anymore? Maybe just switch off Copilot, and have people who think it might produce useful comments activate it manually for specific commits? I don't really care too much about the specifics; any improvement to this situation is welcome.
Regards, Martin.
-------- Forwarded Message -------- Subject: Re: [ruby/ruby] Reject reopening `false` when assigned to constant (PR #18064) Date: Sat, 25 Jul 2026 02:57:24 -0700 From: Earlopain <notifications@github.com> Reply-To: ruby/ruby <reply+AAGHDTMCZMSKXP3WLV2J543K3XQJJEVBNHHQAAAAAEUIY3SX@reply.github.com> To: ruby/ruby <ruby@noreply.github.com> CC: Subscribed <subscribed@noreply.github.com>
Earlopain left a comment (ruby/ruby#18064)
Thanks to the stochastic model for regurgitating what I have already written in 10x the verbosity, much appreciated.
-- Reply to this email directly or view it on GitHub: https://github.com/ruby/ruby/pull/18064#issuecomment-5078055845 You are receiving this because you are subscribed to this thread.
Message ID: <ruby/ruby/pull/18064/c5078055845@github.com>
______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
-- Prof. Dr.sc. Martin J. Dürst Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara 252-5258 Japan