peterxcli commented on PR #10751: URL: https://github.com/apache/ozone/pull/10751#issuecomment-5032623286
> How about we just merge this first then seek for other solution after? @adoroszlai @jojochuang @ayushtkn what do you think, seems like we don't have a clear consensus at this moment. 1. By merging this, we just go back to previous github PR collaborate workflow, which we have been doing in this way for so many years. 2. we can open another PR for the new copilot setting after we have good understanding on how the copilot and ask infra works. 3. base on my current observation, if the PR author has copilot pro or sth, then the copilot review is triggered everytime they push, and consume their quota. but if user dont have, nothing would happen. (btw the copilot review is actually really quota-consuming and easy to hit the limit so "Copilot was unable to review this pull request because the user who requested the review has reached their quota limit." start to appearing. <img width="389" height="116" alt="image" src="https://github.com/user-attachments/assets/e9b9cde4-48f6-4987-90e2-2e6d34beaf7c"; /> <img width="195" height="284" alt="image" src="https://github.com/user-attachments/assets/40283937-3d27-4a36-90cb-df0e9f87950a"; /> above charts show that my quota is occupy at 70% in one day just for reviewing my draft pr: #10743. I don't use github copilot for other usage tho. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
