-
-
Notifications
You must be signed in to change notification settings - Fork 1
Ready To merge section #6
Comments
Thank for for the issue ❤️ I saw it last night but I didn't see an obvious solution I was thinking a JSON list which would be easy. Any Ideas? |
I was thinking dumb full text search in conan-io/conan-center-index#2857 (comment) |
Hmmm there have been a few failures post code review changes, it's worth noting 🤔 Out of curiosity how does it impact your decision to review? |
I won't take a look to any PR which already has sufficient reviews (except cases were I have a direct interest in the package). It saves both my time, and also useless notifications to everybody else. I have the same reasoning for PR with a failed status |
I find the stability unreliable, if there's a fail there's usually a label and I filter on that... however the case were CI is stuck might be interesting |
Ok, I did not know you filtered on labels. The only missing case is if the contributor did not request access on conan-io/conan-center-index#4 (which makes conan-io/conan-center-index#3724 ready to be merged) |
No the "No beta" label was removed... its the CI that's failed and no one has restarted hence #6 (comment) above |
https://docs.github.com/en/free-pro-team@latest/rest/reference/repos#statuses Supposedly support by underlying library UPDATE:
|
all approvals are still displayed and it takes one approval from anyone to have it displayed. start of #6
thank you, it's perfect ! |
That's a very nice addition, but you should count only approved reviewers (listed in conan-io/conan-center-index#2857 (comment)), otherwise prs like conan-io/conan-center-index#4079 are marked as ready to merge, whereas they are still missing some reviews.
EDIT: also, could you add a column giving the status of the PR (success./failure/pending) ?
The text was updated successfully, but these errors were encountered: