frappe/frappe_docker - Open Source PR Review Scorecard

Docker environment for developing, deploying, and running Frappe applications (ERPNext and custom apps) in production and development

C-Rank Grade: A (Welcoming) - 55/100

External PR Merge Rate: 56%

Response Time: 3d

First Timer Success: 75%

Frequently Asked Questions

Is frappe/frappe_docker welcoming to first-time open-source contributors?

frappe/frappe_docker has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in frappe/frappe_docker respond to incoming external pull requests in approximately 60.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 55.5 C-Rank™ score (A Tier) represent?

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 55.5 places frappe/frappe_docker in the A tier.

What is the external contributor pull request merge rate for frappe/frappe_docker?

The external contributor pull request merge rate for frappe/frappe_docker is 55.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in frappe/frappe_docker?

frappe/frappe_docker does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

frappe
frappe/frappe_dockerA•Welcoming2.5k
GitHub
Back to Explorer
frappe

frappe/frappe_docker

2,509
InactiveA•Welcoming(55/100)Python

Docker environment for developing, deploying, and running Frappe applications (ERPNext and custom apps) in production and development

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.9/10
Patience Score
8.2/10
Nitpick Rate
26%

Balanced & professional review environment in frappe/frappe_docker. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
55.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
75.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
10 core
Highly collaborative maintainer core
Diagnostic Health HUD
55.7%
Merge Gauge
75.0%
1st-Timer
Community Vibe45/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for frappe/frappe_docker
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/frappe/frappe_docker)](https://getmerged.abhishekco.de/frappe/frappe_docker?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Idea I really like the devcontainer setup in frappe_docker, but working with AI agents in this environment is currently not as straightforward as I would like. I would like to discuss how we could make the existing development setup easier for agents to use, including agents running outside the container. Ideally, an agent could: Start and configure a development environment through the CLI Run commands, tests and builds inside that environment Create separate environments for parallel tasks where needed Delegate work to another agent running inside a container and collect its results Stop and clean up the environments it created The Dev Container CLI already supports starting environments and executing commands inside them. The agent delegation part would depend on the capabilities of the agent tooling we want to support. Skills and setup Some frappe_docker-specific skills could describe how to start the environment, work with apps and sites, run tests, and troubleshoot common probl

📅 Opened Oct 5, 2026💬 1 comment
Quality: 90/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for frappe/frappe_docker

When evaluating whether to contribute to frappe/frappe_docker, 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 frappe/frappe_docker acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to frappe/frappe_docker

01

Is frappe/frappe_docker welcoming to first-time open-source contributors?

frappe/frappe_docker has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 55.5 C-Rank™ score represent?

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 55.5 places frappe/frappe_docker in the Welcoming tier.

04

What is the external contributor pull request merge rate for frappe/frappe_docker?

The external pull request merge rate is 55.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in frappe/frappe_docker?

frappe/frappe_docker does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for frappe/frappe_docker 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.