Kubernetes based Cloud Development Environments for Enterprise Teams
C-Rank Grade: S (Elite) - 79/100
External PR Merge Rate: 91%
Response Time: 3h
First Timer Success: 100%
eclipse-che/che has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eclipse-che/che respond to incoming external pull requests in approximately 2.7 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 78.5 places eclipse-che/che in the S tier.
The external contributor pull request merge rate for eclipse-che/che is 91.3%, based on public PR activity from non-core contributors.
eclipse-che/che currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Kubernetes based Cloud Development Environments for Enterprise Teams
Active maintainer team in eclipse-che/che welcoming community pull requests and bug fixes.
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/eclipse-che/che?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~13 hours (41% approval). Keep your diff compact for rapid review.
Is your enhancement related to a problem? Please describe In some cases of a long-running job (Claude code review, batch of data processing), I would like to run those steps in chemuxer or herdr and switch to VsCode to review what was done without having to commit a possibly wrong code to git. Another use-case i have is when i'm out of office i use only the web vscode, and when i'm at office i use the vscode desktop (and i would like to stop having two workspace) Describe the solution you'd like In the advanced panel, I would like to switch IDE Describe alternatives you've considered No response Additional context No response
Is your enhancement related to a problem? Please describe For practicability reasons, I've set my default PVC size to 10Gb. Sometime i end up filling my workspace PVC and can’t start (project-clone simply fail and crash if there is no space left on the device). One of the cases i have happened while working on a pretty big rust project that filled a whole 150Gb of storage in about an hour (always happen if you try to upgrade all your packages). Describe the solution you'd like I would like two things: knowing the max size of the PVC ( and the current usage in a workspace by doing a df -h in project root ?) ( in the details tab ?) being hable to resize PVC with a +5Gb button or a number input (most likely in the advanced tab) Describe alternatives you've considered No response Additional context No response
Is your task related to a problem? Please describe s390x builds in che-dashboard CI currently use QEMU emulation, which is slower and less reliable than native execution. This causes flaky CI failures and longer build times for s390x architecture jobs. Describe the solution you'd like Enable IBM self-hosted s390x GitHub Actions runners for the eclipse-che/che-dashboard repository via the IBM/actionspz service (https://github.com/IBM/actionspz). Projects need to be reviewed for eligibility before they're on-boarded (we see no problems with che-dashboard in this regard). You can learn more about the service via our FAQ: https://github.com/IBM/actionspz/blob/main/docs/FAQ.md Describe alternatives you've considered No response Additional context s390x support was enabled for che-dashboard and merged in PR - eclipse-che/che-dashboard#1595 IBM's GitHub Actions self-hosted runners are available to use. Che Dashboard Reviewer, @akurinnoy, quoted: "QEMU emulation for s390x is significantly sl
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 eclipse-che/che, 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 eclipse-che/che acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.3% were successfully merged into the primary branch.
eclipse-che/che has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 78.5 places eclipse-che/che in the Elite tier.
The external pull request merge rate is 91.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eclipse-che/che 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 eclipse-che/che 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.