Odoo Purchases, Workflow and Organization
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 48%
Response Time: 1h
First Timer Success: 86%
OCA/purchase-workflow has a recorded first-timer success rate of 85.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in OCA/purchase-workflow respond to incoming external pull requests in approximately 1.4 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 60.6 places OCA/purchase-workflow in the A tier.
The external contributor pull request merge rate for OCA/purchase-workflow is 48.5%, based on public PR activity from non-core contributors.
OCA/purchase-workflow currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in OCA/purchase-workflow. Reviews community pull requests with focus on project quality.
Discussions in OCA/purchase-workflow focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/OCA/purchase-workflow?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (61% approval). Large PRs (>500 lines) take ~7 hours (22% approval). Keep your diff compact for rapid review.
Todo https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-20.0 Modules to migrate account_fiscal_position_allowed_journal_purchase partner_supplierinfo_smartbutton procurement_purchase_no_grouping product_main_seller product_supplier_code_purchase purchase_advance_payment purchase_all_shipments purchase_allowed_product purchase_auto_bill_on_receipt purchase_default_terms_conditions purchase_delivery_split_date purchase_deposit purchase_exception purchase_force_invoiced purchase_invoice_method purchase_landed_cost purchase_last_price_info purchase_line_reassign purchase_no_rfq purchase_order_approved purchase_order_archive purchase_order_general_discount purchase_order_line_deep_sort purchase_order_line_description purchase_order_line_menu purchase_order_line_price_unit_digits purchase_order_line_sequence purchase_order_line_stock_available purchase_order_owner purchase_order_secondary_unit purchase_order_supplierinfo_update purchase_order_t
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 OCA/purchase-workflow, 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 OCA/purchase-workflow acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.5% were successfully merged into the primary branch.
OCA/purchase-workflow has a recorded first-timer success rate of 85.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 60.6 places OCA/purchase-workflow in the Welcoming tier.
The external pull request merge rate is 48.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OCA/purchase-workflow currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for OCA/purchase-workflow 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.