prince-chrismc / conan-center-index-pending-review

A simple repository to automatically track which conan-center-index pull requests are ready for review
https://prince-chrismc.github.io/conan-center-index-pending-review/
MIT License
14 stars 1 forks source link

Pull Requests Ready to be Reviewed #1

Open prince-chrismc opened 3 years ago

prince-chrismc commented 3 years ago

:sparkles: Summary of Pull Requests Pending Review!

:ballot_box_with_check: Selection Criteria:

Legend

Icon Description
:new: Adding a recipe which does not yet exist
:memo: Modification to an existing recipe
:green_book: Documentation change [1]
:gear: GitHub configuration/workflow changes [1]
:stopwatch: or :warning: The commit status does not indicate success [2]
:bell: The last review was more than 12 days ago
:eyes: It's been more than 3 days since the last commit and there are no reviews

:nerd_face: Please Review!

There are 215 pull requests currently under way :detective:

PR By Opened Recipe Weight Reviews Last :stop_sign: Blockers :star2: Approvers
#16074 Jihadist Feb 16 :new: krb5 L 1 Feb 25 :bell: valgur
#18570 samuel-emrys Jul 16 :memo: xorg :green_circle: XS 4 Mar 24 :bell: jwillikers, SSE4, valgur
#18672 valgur Jul 19 :memo: kcov L 1 Feb 26 :bell: jwillikers
#18680 valgur Jul 19 :memo: kealib L 2 Jan 16 :bell:
#18715 valgur Jul 20 :memo: scc L 1 Mar 25 :bell: jwillikers
#18739 valgur Jul 20 :memo: unleash-client-cpp L 1 Mar 25 :bell: jwillikers
#18810 valgur Jul 22 :memo: daggy L 3 Apr 3 :bell:
#18812 valgur Jul 22 :memo: libjxl XL 3 Apr 30 jwillikers
#18816 valgur Jul 22 :memo: dd-opentracing-cpp L 4 May 7 danimtb, DS-Alex-AG
#18820 valgur Jul 22 :memo: pagmo2 L 1 Mar 25 :bell: jwillikers
#18837 valgur Jul 22 :stopwatch: qcoro L 0 :eyes:
#18842 valgur Jul 23 :memo: azure-storage-cpp L 2 Apr 20 :bell: jwillikers
#18852 valgur Jul 23 :memo: libtommath L 3 Apr 9 :bell:
#18938 valgur Jul 28 :memo: makefile-project-workspace-creator M 3 Mar 24 :bell: jwillikers
#18948 valgur Jul 28 :memo: hiredis L 1 Mar 25 :bell: jwillikers
#18949 valgur Jul 28 :memo: userspace-rcu L 1 Mar 25 :bell: jwillikers
#18950 valgur Jul 28 :memo: pbc L 1 Mar 25 :bell: jwillikers
#18979 valgur Jul 31 :memo: libfabric L 1 Mar 1 :bell: jwillikers
#18986 valgur Jul 31 :memo: librhash L 1 Mar 25 :bell: jwillikers
#19082 bog-dan-ro Aug 7 :stopwatch: qt :green_circle: XS 4 Mar 24 :bell: jwillikers, MartinDelille
#19234 cjbradfield Aug 16 :new: quictls-openssl XL 0 :eyes:
#19239 valgur Aug 17 :memo: pro-mdnsd L 1 Aug 21 :bell: steinerthomas
#19726 bryce-cahill Sep 10 :memo: pcre2 M 3 Mar 24 :bell: SpaceIm, valgur
#19942 Woazim Sep 18 :memo: imagl M 1 Mar 24 :bell: valgur
#19980 valgur Sep 20 :memo: glslang L 6 Apr 21 :bell: jwillikers
#20172 Wawha Sep 27 :stopwatch: tensorflow-lite :green_circle: XS 2 Mar 24 :bell: valgur
#20270 valgur Oct 2 :memo: libsndfile M 2 Oct 27 :bell: ericLemanissier, jwillikers
#20290 jwillikers Oct 2 :memo: libsystemd L 2 Mar 24 :bell: valgur
#20336 SpaceIm Oct 3 :memo: boost :green_circle: XS 3 Feb 28 :bell: RubenRBS jwillikers, valgur
#20369 SpaceIm Oct 5 :stopwatch: pipes :blue_square: S 2 Mar 24 :bell: jwillikers, valgur
#20373 jwillikers Oct 5 :new: libblkid M 1 Mar 19 :bell: valgur
#20381 SpaceIm Oct 5 :memo: sdl L 10 Mar 22 :bell: jwillikers, valgur
#20392 bverhagen Oct 6 :stopwatch: onnxruntime M 11 Oct 31 :bell: jwillikers
#20465 gjasny Oct 9 :memo: resiprocate L 2 Feb 23 :bell: valgur
#20507 jwillikers Oct 10 :memo: libmount M 3 Mar 26 :bell:
#20586 valgur Oct 16 :memo: pcre2 M 1 Nov 20 :bell: jwillikers
#20725 mayeut Oct 21 :stopwatch: podofo :green_circle: XS 0
#20987 toge Nov 8 :stopwatch: octo-keygen-cpp :green_circle: XS 0 :eyes:
#21085 SpaceIm Nov 12 :memo: msdfgen L 4 Mar 17 :bell: jwillikers, valgur
#21207 toge Nov 18 :memo: structopt :green_circle: XS 4 Feb 28 :bell: uilianries jwillikers, valgur
#21238 valgur Nov 19 :memo: brunsli :green_circle: XS 2 Jan 3 :bell: jwillikers, ericLemanissier
#21246 SpaceIm Nov 19 :memo: libdisplay-info :blue_square: S 3 Feb 23 :bell: jwillikers, valgur
#21389 valgur Nov 26 :memo: getdns L 1 Mar 25 :bell: jwillikers
#21391 ashley-b Nov 27 :memo: qwt L 4 Mar 25 :bell:
#21512 valgur Nov 30 :memo: proj L 3 Apr 18 :bell:
#21558 mayeut Dec 3 :memo: libcurl L 1 Dec 7 :bell: uilianries
#21575 ngrodzitski Dec 3 :memo: logr M 14 Apr 9 :bell: RubenRBS uilianries, valgur
#21622 valgur Dec 5 :memo: protobuf L 0 :eyes:
#21626 SpaceIm Dec 5 :memo: ginkgo M 5 Mar 24 :bell: jwillikers, valgur
#21664 valgur Dec 6 :memo: sundials M 3 Apr 18 :bell: danimtb jwillikers
#21666 valgur Dec 6 :memo: seqan3 :blue_square: S 1 Mar 25 :bell: jwillikers
#21689 PodnimatelPingvinov Dec 8 :stopwatch: clickhouse-cpp :green_circle: XS 1 Mar 24 :bell: valgur
#21713 tpaustian Dec 11 :stopwatch: boost :green_circle: XS 1 Mar 24 :bell: valgur
#21740 rainman110 Dec 13 :new: gtlab-logging M 6 May 9 valgur
#21763 talyz Dec 14 :memo: tensorflow-lite L 5 Mar 24 :bell: jwillikers, valgur
#21767 toge Dec 14 :memo: wasm-micro-runtime M 1 Mar 24 :bell: valgur
#21855 valgur Dec 21 :memo: aeron :blue_square: S 1 Mar 25 :bell: jwillikers
#21910 valgur Dec 26 :memo: mariadb-connector-c L 1 Mar 25 :bell: jwillikers
#21926 valgur Dec 26 :memo: armadillo L 2 Jan 10 :bell:
#21927 valgur Dec 26 :memo: aruco :blue_square: S 3 Mar 27 :bell: jwillikers
#21945 toge Dec 26 :memo: leptonica M 3 Mar 26 :bell: valgur
#21954 valgur Dec 26 :stopwatch: libsigcpp L 1 Jan 6 :bell: RubenRBS
#21985 mayeut Dec 27 :memo: dcmtk :blue_square: S 3 Apr 10 :bell:
#21987 valgur Dec 27 :memo: libaec L 1 Feb 26 :bell: jwillikers
#21989 valgur Dec 27 :new: libmd M 1 Mar 22 :bell: jwillikers
#22002 valgur Dec 27 :memo: sdl_net :blue_square: S 1 Mar 22 :bell: jwillikers
#22019 valgur Dec 28 :memo: apr-util L 1 Mar 25 :bell: jwillikers
#22023 valgur Dec 28 :memo: glibmm L 1 Mar 25 :bell: jwillikers
#22040 valgur Dec 28 :memo: tk L 0 :eyes:
#22094 anonymousdouble Jan 1 :stopwatch: dbus :green_circle: XS 0 :eyes:
#22120 toge Jan 3 :stopwatch: mbits-lngs :green_circle: XS 1 Mar 24 :bell: valgur
#22132 jwillikers Jan 3 :memo: qt :blue_square: S 1 Apr 19 :bell:
#22152 valgur Jan 4 :memo: pcl L 2 Apr 30
#22155 fdgStilla Jan 4 :memo: onnxruntime M 1 Mar 24 :bell: valgur
#22165 wu-vincent Jan 5 :new: minhook M 2 Mar 24 :bell: valgur
#22197 valgur Jan 7 :memo: libxpm M 2 Apr 25 :bell: jwillikers
#22204 ericLemanissier Jan 8 :memo: gdal L 8 May 6 jwillikers
#22229 valgur Jan 9 :new: libcudacxx M 2 Apr 26 :bell: jwillikers
#22267 jacobfriedman Jan 11 :stopwatch: libgit2 M 0 :eyes:
#22290 valgur Jan 13 :memo: cimg L 1 Mar 5 :bell:
#22318 valgur Jan 13 :memo: libbasisu L 1 Mar 25 :bell: jwillikers
#22325 valgur Jan 14 :green_book: docs L 2 Jan 15 :bell:
#22353 valgur Jan 15 :memo: llvm-openmp XL 7 Apr 30 jwillikers
#22406 st9007a Jan 17 :memo: aws-c-sdkutils :blue_square: S 4 Mar 25 :bell: valgur
#22418 valgur Jan 18 :memo: tesseract :green_circle: XS 1 Mar 25 :bell: jwillikers
#22427 st9007a Jan 18 :memo: aws-c-cal :green_circle: XS 2 Mar 25 :bell: valgur
#22432 anthonyliot Jan 19 :stopwatch: libx264 :green_circle: XS 3 Mar 24 :bell: valgur
#22456 toge Jan 20 :stopwatch: proposal :green_circle: XS 1 Mar 24 :bell: valgur
#22539 Artalus Jan 25 :memo: abseil :green_circle: XS 1 Jan 29 :bell:
#22557 fdgStilla Jan 26 :stopwatch: onnxruntime L 0 :eyes:
#22574 toge Jan 28 :memo: reflect-cpp :blue_square: S 9 May 9 franramirez688 RubenRBS, uilianries, czoido
#22575 Ahajha Jan 28 :memo: sdl_image :blue_square: S 3 Apr 25 :bell:
#22584 choll Jan 29 :memo: xtr :green_circle: XS 1 Mar 24 :bell: valgur
#22614 RazielXYZ Feb 1 :memo: async_simple L 12 May 9 danimtb
#22657 StellaSmith Feb 5 :memo: glm M 2 Mar 19 :bell: jwillikers, valgur
#22667 valgur Feb 5 :memo: gperftools M 4 Mar 25 :bell: jwillikers
#22690 Kaaml Feb 6 :memo: date :green_circle: XS 2 Mar 24 :bell: ericLemanissier
#22692 Nekto89 Feb 6 :green_book: docs :blue_square: S 0 :eyes:
#22698 toge Feb 7 :new: battery-embed M 1 Mar 24 :bell:
#22708 toge Feb 7 :memo: stringzilla L 6 Mar 24 :bell:
#22747 jeremy-rifkin Feb 11 :stopwatch: folly :green_circle: XS 1 Mar 24 :bell: valgur
#22795 Alex-PLACET Feb 16 :memo: sqlitecpp :blue_square: S 8 Mar 24 :bell:
#22823 toge Feb 19 :new: fpng M 2 Mar 24 :bell: valgur
#22832 klausholstjacobsen Feb 20 :stopwatch: openssl :blue_square: S 1 Mar 24 :bell: valgur
#22851 valgur Feb 22 :memo: stdgpu :blue_square: S 1 Mar 13 :bell: jwillikers
#22861 toge Feb 22 :memo: miniscript L 4 Mar 24 :bell: valgur
#22865 samuaz Feb 22 :new: mariadb-connector-cpp L 4 Mar 24 :bell:
#22910 Tradias Feb 27 :memo: asio-grpc M 1 Mar 24 :bell: valgur
#22951 mologie Mar 1 :memo: xnnpack :blue_square: S 1 Mar 24 :bell: valgur
#22952 jwillikers Mar 1 :memo: libselinux L 1 Mar 24 :bell:
#22958 jwillikers Mar 2 :memo: fltk :green_circle: XS 0 :eyes:
#22983 Ahajha Mar 5 :memo: re2 :blue_square: S 1 Mar 19 :bell: valgur
#22991 jwillikers Mar 5 :new: pipewire L 6 Mar 26 :bell:
#22994 irieger Mar 5 :stopwatch: openexr :green_circle: XS 1 Mar 24 :bell: valgur
#22997 planetmarshall Mar 5 :memo: llvm-core XL 8 Apr 19 :bell: jwillikers
#22998 toge Mar 6 :memo: aws-c-auth :blue_square: S 3 Apr 11 :bell:
#22999 toge Mar 6 :stopwatch: aws-c-mqtt :green_circle: XS 2 Mar 25 :bell: jwillikers, valgur
#23043 irieger Mar 10 :stopwatch: opencolorio :green_circle: XS 1 Mar 24 :bell: valgur
#23052 uilianries Mar 11 :green_book: docs :blue_square: S 2 Mar 11 :bell: jcar87
#23066 YSaxon Mar 11 :stopwatch: libffi :blue_square: S 1 Mar 24 :bell:
#23080 RazielXYZ Mar 13 :new: gaia-ecs M 5 Apr 16 :bell: jwillikers
#23087 spiderkeys Mar 13 :new: libsndio M 11 Apr 2 :bell:
#23095 sophieeihpos Mar 14 :memo: protobuf L 10 Apr 26 :bell:
#23131 mayeut Mar 17 :stopwatch: libsixel :green_circle: XS 1 Mar 24 :bell:
#23134 mayeut Mar 17 :memo: leptonica M 2 Apr 1 :bell: valgur
#23135 mayeut Mar 17 :stopwatch: itk :blue_square: S 1 Mar 24 :bell:
#23138 mayeut Mar 17 :stopwatch: freeimage :green_circle: XS 2 Apr 20 :bell: jwillikers, valgur
#23143 mayeut Mar 17 :stopwatch: gdk-pixbuf :blue_square: S 1 Mar 24 :bell:
#23147 mayeut Mar 17 :stopwatch: opencv :green_circle: XS 1 Mar 24 :bell:
#23148 mayeut Mar 17 :memo: opencv :blue_square: S 1 Mar 24 :bell:
#23153 js-nano Mar 18 :memo: grpc :blue_square: S 1 Mar 24 :bell: valgur
#23214 valgur Mar 22 :new: vlfeat L 0 :eyes:
#23217 StellaSmith Mar 22 :stopwatch: libtiff :green_circle: XS 1 Mar 24 :bell: valgur
#23221 toge Mar 23 :memo: mold :green_circle: XS 3 May 3 jwillikers
#23223 valgur Mar 23 :memo: premake L 5 Mar 23 :bell:
#23241 toge Mar 25 :stopwatch: ssp :green_circle: XS 1 Mar 25 :bell: valgur
#23252 valgur Mar 25 :stopwatch: cfitsio L 0 :eyes:
#23253 valgur Mar 25 :memo: dav1d M 0 :eyes:
#23255 valgur Mar 25 :memo: harfbuzz L 3 Apr 1 :bell: RubenRBS jwillikers
#23256 valgur Mar 25 :memo: hwloc :blue_square: S 1 Mar 25 :bell:
#23257 valgur Mar 25 :memo: jasper L 1 Apr 1 :bell: jwillikers
#23270 xyz1001 Mar 26 :new: platformfolders M 1 May 9 danimtb
#23272 johningve Mar 26 :memo: glfw :blue_square: S 2 Apr 9 :bell: jwillikers
#23304 gegles Mar 29 :memo: openssl :blue_square: S 4 Apr 26 :bell: jcar87 valgur, Croydon
#23319 toge Mar 31 :memo: harfbuzz :blue_square: S 3 May 9 jwillikers
#23336 valgur Apr 2 :memo: libcvd :blue_square: S 0 :eyes:
#23346 sizeak Apr 2 :memo: android-ndk :blue_square: S 0 :eyes:
#23347 MikeLankamp Apr 2 :memo: diligent-core L 1 Apr 3 :bell: valgur
#23359 AndreyMlashkin Apr 3 :stopwatch: gcc :green_circle: XS 0 :eyes:
#23362 Ahajha Apr 4 :memo: libffi L 1 Apr 8 :bell:
#23383 valgur Apr 5 :memo: libpcap M 1 Apr 9 :bell: jwillikers
#23392 gouriano Apr 5 :memo: ncbi-cxx-toolkit-public XL 0
#23393 valgur Apr 5 :memo: onetbb :blue_square: S 1 Apr 9 :bell: jwillikers
#23394 Ahajha Apr 6 :memo: cpython L 11 Apr 10 :bell: jwillikers
#23409 mayeut Apr 7 :memo: onnxruntime L 0 :eyes:
#23429 toge Apr 9 :memo: aws-lambda-cpp :blue_square: S 0 :eyes:
#23481 elvisdukaj Apr 11 :memo: mingw-builds M 1 Apr 17 :bell:
#23502 Jie-Cheng Apr 12 :stopwatch: simdjson :green_circle: XS 0 :eyes:
#23517 mayeut Apr 13 :stopwatch: qt :blue_square: S 4 May 7 jwillikers, MartinDelille
#23521 toge Apr 14 :new: tidwall-neco M 1 Apr 15 :bell:
#23530 valgur Apr 15 :new: coin-buildtools M 0 :eyes:
#23539 tkhyn Apr 15 :memo: osqp L 6 Apr 15 :bell:
#23559 valgur Apr 15 :memo: glib M 2 May 8 ericLemanissier
#23571 ericLemanissier Apr 16 :memo: qt XL 9 Apr 23 :bell: jwillikers
#23594 uilianries Apr 17 :gear: .c3i :blue_square: S 3 Apr 17 :bell: jcar87 RubenRBS, jwillikers
#23598 MartinDelille Apr 17 :memo: openapi-generator :blue_square: S 0 :eyes:
#23602 adamws Apr 17 :memo: cyrus-sasl :green_circle: XS 2 Apr 20 :bell: valgur
#23607 Arenoros Apr 17 :stopwatch: lief M 0 :eyes:
#23612 basiliscos Apr 17 :memo: util-linux-libuuid :green_circle: XS 2 Apr 20 :bell: Ahajha
#23626 mayeut Apr 17 :stopwatch: xmlsec :green_circle: XS 0 :eyes:
#23629 toge Apr 18 :memo: duckdb M 1 May 9 RubenRBS
#23632 pichi-router Apr 18 :memo: botan :green_circle: XS 1 Apr 20 :bell:
#23639 HappySeaFox Apr 18 :memo: sail :green_circle: XS 0 :eyes:
#23645 anton-danielsson Apr 18 :memo: qcustomplot M 7 Apr 20 :bell: ericLemanissier
#23648 Ahajha Apr 19 :memo: cpython :green_circle: XS 0 :eyes:
#23653 robomics Apr 19 :stopwatch: boost :green_circle: XS 0 :eyes:
#23654 robomics Apr 19 :memo: libarchive :green_circle: XS 0 :eyes:
#23656 TheHugeManatee Apr 19 :memo: kdbindings :green_circle: XS 0 :eyes:
#23663 trns1997 Apr 19 :new: azure-sdk-for-cpp L 2 May 3
#23666 mayeut Apr 20 :stopwatch: libxmlpp :green_circle: XS 0
#23667 mayeut Apr 20 :stopwatch: libspatialite :green_circle: XS 2 May 8 jwillikers
#23668 mayeut Apr 20 :stopwatch: libgphoto2 :green_circle: XS 0
#23671 laci-aura Apr 20 :new: zxcvbn L 0 :eyes:
#23677 toge Apr 20 :memo: metall :blue_square: S 0 :eyes:
#23680 valgur Apr 20 :memo: flac :blue_square: S 0 :eyes:
#23683 valgur Apr 20 :memo: libssh2 M 0 :eyes:
#23695 dbolduc Apr 22 :memo: google-cloud-cpp L 0 :eyes:
#23696 toge Apr 22 :memo: oatpp L 1 Apr 22 :bell:
#23704 anton-danielsson Apr 22 :memo: openscenegraph XL 1 May 9 czoido
#23709 toge Apr 23 :memo: mimalloc L 0 :eyes:
#23720 valgur Apr 23 :new: libosmium M 3 Apr 30
#23731 tbeu Apr 23 :memo: laszip M 0 :eyes:
#23733 PLeVasseur Apr 23 :new: up-cpp L 0 :eyes:
#23735 valgur Apr 23 :memo: assimp :blue_square: S 1 Apr 28
#23757 jcar87 Apr 25 :gear: .github L 2 Apr 25 :bell:
#23762 lubomirjurukov Apr 25 :stopwatch: ixwebsocket :green_circle: XS 0 :eyes:
#23779 SpaceIm Apr 26 :memo: glfw :green_circle: XS 2 May 2 jwillikers
#23780 SpaceIm Apr 26 :memo: xkbcommon :green_circle: XS 1 Apr 27 :bell: jwillikers
#23782 valgur Apr 26 :new: pangolin L 0 :eyes:
#23787 mologie Apr 27 :stopwatch: pybind11_json :green_circle: XS 0 :eyes:
#23788 DoomHammer Apr 27 :memo: ohpipeline :green_circle: XS 0 :eyes:
#23806 mayeut Apr 29 :memo: tar M 2 Apr 30 jwillikers
#23810 toge Apr 29 :memo: libsvtav1 :green_circle: XS 2 Apr 30 jwillikers
#23846 Mi-La May 2 :memo: zserio M 0 :eyes:
#23852 jmdaly May 2 :memo: ouster_sdk :green_circle: XS 1 May 6 valgur
#23853 ericLemanissier May 3 :memo: libwebsockets :blue_square: S 4 May 8 Croydon
#23864 gegles May 3 :stopwatch: restinio :green_circle: XS 0
#23889 valgur May 6 :new: stella-cv-fbow M 2 May 9 RubenRBS
#23890 gegles May 6 :stopwatch: gegles-spdlog_setup :green_circle: XS 1 May 6 hoyhoy
#23894 datalogics-staylor May 6 :memo: qr-code-generator M 0
#23901 toge May 7 :memo: daw_utf_range :blue_square: S 0
#23907 soroosh-sdi May 7 :memo: lzham :blue_square: S 2 May 9 RubenRBS
#23920 franramirez688 May 8 :stopwatch: yomm2 M 2 May 9
#23935 toge May 9 :memo: nghttp3 :green_circle: XS 0
#23937 ErniGH May 9 :stopwatch: freeimage :blue_square: S 2 May 9 RubenRBS

:heavy_check_mark: Ready to Merge

Currently 2 pull requests are waiting to be merged :tada:

PR By Opened Recipe Reviews :star2: Approvers
#22876 RubenRBS Feb 24 :new: dispenso 3 uilianries, jwillikers
#23936 ErniGH May 9 :memo: libelfin 2 RubenRBS, uilianries

:clipboard: Statistics

:warning: These are just rough metrics counting the labels and may not reflect the actual state of pull requests

Raw JSON data

:bar_chart: Open Versus Merged

Legend

Pull requests are depicted as:

For reference:

ovm

:hourglass: Time Spent in Review

If you are wondering how long it will take for you pull request to get merged; this graph should give you an idea.

tir

Found this useful? Give it a :star: :pray:

uilianries commented 3 years ago

3427 Still waiting for improvements.

3877 LGTM

3962 LGTM

4032 LGTM

mental note: Track my blocked review, otherwise I can delay more PRs.

SSE4 commented 3 years ago

@prince-chrismc may you add some legend with icons meaning?

prince-chrismc commented 3 years ago

may you add some legend with icons meaning?

That sounds like an excellent idea! I'll see if I can squeeze it in today/tomorrow πŸ˜„

prince-chrismc commented 3 years ago

@SSE4 I updated the code to add a legend. Let me know if it helps

mathbunnyru commented 3 years ago

@prince-chrismc small note: Age: 76d11h16m40.084126774s What does it mean and it doesn't look pretty =)

prince-chrismc commented 3 years ago

It's Golangs internal date formatting πŸ‘Ύ Is the average age of the pull requests... there's a lot of pull requests bloating the number

mathbunnyru commented 3 years ago

It's Golangs internal date formatting πŸ‘Ύ Is the average age of the pull requests... there's a lot of pull requests bloating the number

Thanks for the information. If you have some spare time, I would be glad if you changed formatting and the wording to smth like Average PR age.

prince-chrismc commented 3 years ago

Done!

ericLemanissier commented 3 years ago

Is it me, or was the PR https://github.com/conan-io/conan-center-index/pull/5440 never mentioned in this post ? EDIT: it's expected, because all the reviews happened in less than an hour

prince-chrismc commented 3 years ago

Someone was really busy...

image

dvirtz commented 3 years ago

should my PRs appear here?

https://github.com/conan-io/conan-center-index/pull/5605 https://github.com/conan-io/conan-center-index/pull/5606 https://github.com/conan-io/conan-center-index/pull/5914

prince-chrismc commented 3 years ago

5605 has no approval, 5606 is labeled, 5914 no approvals

I will one day expand this to include PRs like yours but we have so many open as it is... I assume if someone starts reviewing they see it through but you just convinced me that's not always true...

πŸ€”

redradist commented 3 years ago

Can somebody review this MR Initial support for wasmtime package ?

prince-chrismc commented 3 years ago

Please be patient! https://github.com/conan-io/conan-center-index/pull/6083#issuecomment-873398554 just passed 11 minutes ago, and it's on the board... If you look at time in review graph it's very normal for it to take ~7 days.

There's a lot of PRs and we try our best to get to them all

SSE4 commented 3 years ago

@prince-chrismc I see that builds with running (waiting for CI) status are added into the table. is it expected?

prince-chrismc commented 3 years ago

I see that builds with running (waiting for CI) status are added into the table. is it expected?

Yes! I am optimistic they will pass. It's the "ready to merge" where I note a warning

madebr commented 3 years ago

@prince-chrismc I have an idea for a graph, but am uncertain whether it will work. On the x-axis: datetime, y-axis: days open The graph would be a boxplot with (colored) lines of 10, 20, ... , 90, 100% of pr's were open this long. I think very old pr's (such as my cpython pr) are skewing your plots.

Is there an easy way to get the raw data? What I need is, for each pr: datetime opened, datetime closed. To filter further, the results of c3i would also be useful: result + datetime.

It would be nice if your github actions would publish this data as an artifact.

prince-chrismc commented 3 years ago

I haven't read your whole comment but there's tons of data we can extra... the visual is limited to OSS graph generators

It would be nice if your github actions would publish this data as an artifact.

It's all pushed to a second branch called [raw-data](https://github.com/prince-chrismc/conan-center-index-pending-review/tree/raw-data)

prince-chrismc commented 3 years ago

I think very old pr's (such as my cpython pr) are skewing your plots.

I 100% agree, I have cut them out of the graph by setting a ceiling... they do not kill the moving average so I still include them and I have limited the start page so not to go so far back... you can see me playing with values here


Since I have a 30 min break, let's see if I understood this...

On the x-axis: datetime, y-axis: days open The graph would be a boxplot with (colored) lines of 10, 20, ... , 90, 100% of pr's were open this long.

Stacked is supported by current library

image

I think it would be more clean then the thin line on the closed date (I did originally use the open date but it did not allow to spot trends)

madebr commented 3 years ago

The graph is more or less what I meant. I propose a color coding from green over orange to red. It feels more "naturel".

I would set y-range to a value that results in a pretty graph. :smile: For the x-range, perhaps we should have a general graph (=several months) and a detailed graph (=last month), such that we can compare how we're doing now compared to X months ago.

I had a look at the raw data, but found it already too summarized. I was hoping to have more details for each pr because the number of days a pr is open is not always useful. It's useful to know whether it was merged in the end, closed by the author, closed by stale-bot, rejected by us, ... Also knowing when c3i started to successfully build a pr is useful, because an old pr that fails to build also skews the data.

prince-chrismc commented 3 years ago

I propose a color coding from green over orange to red. It feels more "natural".

Something like green is the fastest 50% of PRs for that day, orange for 75%, and red is all of them?

I would set y-range to a value that results in a pretty graph.

This is really freaking hard! The library only supports equally spaced values and the majority are tiny numbers but the rest are huge... it's hard to do

For the x-range, perhaps we should have a general graph (=several months) and a detailed graph (=last month), such that we can compare how we're doing now compared to X months ago.

I really love this idea! it's already a task I have written in #11

I had a look at the raw data, but found it already too summarized. I was hoping to have more details for each pr because the number of days a pr is open is not always useful. It's useful to know whether it was merged in the end, closed by the author, closed by stale-bot, rejected by us

This bot only exclusively looks at those that were merged... so nothing else is present (i did not find them valuable).

I'd love to expand the bot to include more information... per day counts are hard since they need time to accumulate... how ever inspecting comments each PR is doable. example

β†ͺ️ If you have ideas or suggestions, I'd love to add them.

Also knowing when c3i started to successfully build a pr is useful, because an old pr that fails to build also skews the data.

Far too often I see us helping the author getting it to pass (there tends to be reviews/comments before it passes and I am not sure how well that would work with the proliferant "Unexpected Error" plague 😷) ... on some occasions we let them drag or put them on hold...

I did consider looking at the "time in review" as the gap from the first to last... how ever I realized sometimes we put comments and not reviews and it made some of the PRs reflect inaccurate very short durations... however 6 months later I am very open to re-opening the topic

prince-chrismc commented 3 years ago

I am shocked we are merging more PRs then closing compared to the past

@madebr How's this? #21

som

madebr commented 3 years ago

Honestly, the graph is not telling me much. Apart from that, it's nice to see that prs are getting merged instead of being wasted/closed. On such long timescales, some averaging is required or data should be grouped per week/month.

If you really want to work further on this, I can only suggest to extract all data and save it to a csv. Perhaps, by playing with the data using pivot tables, trends can become clearer and such graph can be converted into go code.

prince-chrismc commented 3 years ago

Okay, taking some off so I finally have a chance to play with this... I am not sure I'll get exactly what you were hoping for but I really love the idea. (sorry I dont understand your vision)

Here is the last 60 days

ovm

Here is the CCI history

πŸš€ There are weeks we closed every PR 😱

ovm

madebr commented 3 years ago

Nice graph! It immediately tells me that ~10% of all prs get closed without merging. Also, there are few old pr's that just don't get closed and we are unable to get merged.

Using more shades of purple/red, we could how long it took until a pr was closed/merged.

:rocket: There are weeks we closed every PR :scream:

That must have been a productive week! :rofl: What week was it? Perhaps it was a week with only one pr?

Weeks with little activity perhaps don't deserve equal visibility. I currently don't have an idea to account for this though.

prince-chrismc commented 3 years ago

Nice graph!

Thank you! πŸ€—

Weeks with little activity perhaps don't deserve equal visibility.

:100: I was thinking, there's a day with the most opened PRs (it's mid 30s) I can probably pad all of them to that height with alpha... This was weeks with low activity have smaller bars... however I like the color ordering being consistent (it's satisfying to look at).

prince-chrismc commented 3 years ago

52 weeks weighted graph

ovm

Entire history weighted

ovm

prince-chrismc commented 3 years ago

➑️ I can use feedback on the colors

52 weeks weighted + merged in under 7 days

ovm

madebr commented 3 years ago

I think the colors look great! What do the 2 purple shades mean? I miss a legend πŸ˜„ The x and y labels are also not readable.

I like the simplicity of the graph. Btw, it looks like this graph is not very cci specific. So you can re-use it for other projects.

prince-chrismc commented 3 years ago

What do the 2 purple shades mean? I miss a legend

Forgot to write it xD dark purple === less then 7 days to merge

The x and y labels are also not readable.

They do not exist, because of how the graph is made they are not supported I need to play with it a little more see it I can add some text 🀞

it looks like this graph is not very cci specific. So you can re-use it for other projects.

That is absolutely correct, short of the hardcoded API calls but those can easily be changes

madebr commented 3 years ago

Would the graph above, but only applied to:

be useful? These are the 3 main types of prs created. Prs bumping versions should have a shorter "age" then prs adding new recipes.

prince-chrismc commented 3 years ago

One graph for each? Might be interesting to see if adds and modifications have the same trends πŸ€”

If you meant limit the included PRs theres very few, I played with it on the other graph, wasn't worth while

madebr commented 3 years ago

I have another crazy idea. Create a gif/video. You have probably seen those animated videos on https://www.reddit.com/r/dataisbeautiful/. Would it be nice to see grahs like in https://github.com/prince-chrismc/conan-center-index-pending-review/issues/1#issuecomment-903336157, but animated in time?

prince-chrismc commented 3 years ago

I have another crazy idea. Create a gif.

I had the same reaction 🀣 It would be amazing. GIFs are natively support in golang so it should be doable. http://tech.nitoyon.com/en/blog/2016/01/07/go-animated-gif-gen/

Lemiort commented 2 years ago

Um, what? Why my PR is not in the list to review? https://github.com/conan-io/conan-center-index/pull/6944

prince-chrismc commented 2 years ago

Um, what? Why my PR is not in the list to review? conan-io/conan-center-index#6944

Someone reviewed it already and it was not approved

If you have ideas how to catch PRs like that (where someone slacked off on a follow up) I'd be glad to refine my bot :)

madebr commented 2 years ago

@prince-chrismc Why doesn't conan-io/conan-center-index#7190 appear in the list?

prince-chrismc commented 2 years ago

no approval and... it has a review from redradist (which the bot assume you need to make changes) after your last commit.

madebr commented 2 years ago

Ah, thanks for explaining the bot's behavior.

madebr commented 2 years ago

@prince-chrismc This analysis of the cpython git history might interest you: https://lukasz.langa.pl/f15a8851-af26-4e94-a4b1-c146c57c9d20/

MartinDelille commented 2 years ago

My PR doesn't appear here: https://github.com/conan-io/conan-center-index/pull/8554

Any idea?

ericLemanissier commented 2 years ago

maybe because of the Unexpected Error label ? you can probably restart the build to remove it

prince-chrismc commented 2 years ago

maybe because of the Unexpected Error label ? you can probably restart the build to remove it

That was certainly why :+1:

prince-chrismc commented 2 years ago

I need to make graphs just for @SpaceIm πŸ’Ÿ

image

Almost beat your last record

image

prince-chrismc commented 2 years ago

I have another crazy idea. Create a gif/video.

@madebr I've been playing with this got and https://github.com/prince-chrismc/conan-center-index-pending-review/pull/32/commits/1de7c841fe960c2789abd7a7af5f23195edb5d8f which is a loop of the last week of daily summaries

ovm

Thoughts?

kenneth-jia commented 2 years ago

Hi, @prince-chrismc About the https://github.com/conan-io/conan-center-index/pull/11430 , previously it has been approved by @uilianries , while I pushed another small commit after while and re-required the review. Maybe that makes the "Approvers" column empty? Sorry, this is the first time I raised a PR to conan-conter-index and I'm not quite familiar with these procedures. Could you please help tell how long it might take to get the PR merged? πŸ˜… Thanks!

prince-chrismc commented 2 years ago

this is the first time I raised a PR to conan-conter-index and I'm not quite familiar with these procedures.

First and foremost, welcome!

This bot is designed to "closely" follow the https://github.com/conan-io/conan-center-index/blob/master/docs/review_process.md along with the peculiarities of GitHub.

I pushed another small commit after while and re-required the review. Maybe that makes the "Approvers" column empty?

Yes, thats exactly how GitHub tracks approvals! When you push commit's you dismiss stale approvals.

C3i and this bot both count the approvals on the very last commit which is why they go away

Could you please help tell how long it might take to get the PR merged?

If only I could predict the future money

Given the attention in the last 24hrs I'd say it should be the average 5 days, I noticed it's already been 20 days but it should not take much longer 🀞

Neustradamus commented 1 year ago

To follow this ticket :)

ericLemanissier commented 1 year ago

FYI, the same information is available as a full web page at https://prince-chrismc.github.io/conan-center-index-pending-review/

prince-chrismc commented 1 year ago

Just computing the table was 1250 requests https://github.com/prince-chrismc/conan-center-index-pending-review/actions/runs/4345764404/jobs/7590927150 😱 should be working again