Computational geometry in Julia
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 80%
Response Time: 10d
First Timer Success: 57%
JuliaGeometry/Meshes.jl has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in JuliaGeometry/Meshes.jl respond to incoming external pull requests in approximately 240.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.8 places JuliaGeometry/Meshes.jl in the A tier.
The external contributor pull request merge rate for JuliaGeometry/Meshes.jl is 80.3%, based on public PR activity from non-core contributors.
JuliaGeometry/Meshes.jl currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/JuliaGeometry/Meshes.jl?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
The following warnings are being emitted by our test suite: Warning: maximum number of subdivisions reached `maxsubdiv=32768`, try increasing the keyword argument `maxsubdiv`. └ @ HAdaptiveIntegration ~/.julia/packages/HAdaptiveIntegration/OeagO/src/integrate.jl:120 ┌ Warning: maximum number of subdivisions reached `maxsubdiv=32768`, try increasing the keyword argument `maxsubdiv`. └ @ HAdaptiveIntegration ~/.julia/packages/HAdaptiveIntegration/OeagO/src/integrate.jl:120 As far as I know, there is no method to print the exact lines that are emitting the warning, so we need to run tests one by one in the REPL to discover the root of the issue. It is likely emitted by some test that calls centroid as we changed the fallback to use h-adaptive integration.
We still need to adjust the code in a few places to get full interactivity within our recipes. For instance, consider the following MWE: using Meshes using Random import GLMakie as Mke boxes = rand(Box, 10) balls = rand(Ball, 10) tetra = rand(Tetrahedron, 10) geoms = shuffle([boxes; balls; tetra]) fig = Mke.Figure() sld = Mke.Slider(fig[1, 1], range=1:length(geoms)) ax3 = Mke.Axis3(fig[2, 1], aspect=:data) sub = Mke.@lift geoms[1:$(sld.value)] viz!(ax3, sub) Mke.on(sld.value) do i Mke.autolimits!(ax3) end fig Because the slider starts with only the first geometry, the direct access to plot[objectid][] registers a single recipe in the compute graph, no matter how much we move the slider: Meshes.jl/ext/geomset.jl Line 14 in 416dfeb geoms = parent(plot.object[]) We need to refactor the code to handle heterogeneous vectors of geometries. There are other places that rely
The following never finishes for me, the julia process just keeps spinning at 100%: julia> import GeoArtifacts julia> using GeoTables julia> using Meshes #using Plots julia> using CairoMakie julia> BRA = GeoArtifacts.GADM.get("BRA", depth = 0) 1×3 GeoTable over 1 GeometrySet ┌─────────────┬─────────────┬───────────────────────────────┐ │ GID_0 │ COUNTRY │ geometry │ │ Categorical │ Categorical │ MultiPolygon │ │ [NoUnits] │ [NoUnits] │ 🖈 GeodeticLatLon{WGS84Latest} │ ├─────────────┼─────────────┼───────────────────────────────┤ │ BRA │ Brazil │ Multi(1007×PolyArea) │ └─────────────┴
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to JuliaGeometry/Meshes.jl, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of JuliaGeometry/Meshes.jl acknowledge new external contributions in approximately 10 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.3% were successfully merged into the primary branch.
JuliaGeometry/Meshes.jl has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.8 places JuliaGeometry/Meshes.jl in the Welcoming tier.
The external pull request merge rate is 80.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, JuliaGeometry/Meshes.jl currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for JuliaGeometry/Meshes.jl are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.