Manage the lifecycle of Temporal Workers
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 74%
Response Time: 6h
First Timer Success: 73%
temporalio/temporal-worker-controller has a recorded first-timer success rate of 72.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in temporalio/temporal-worker-controller respond to incoming external pull requests in approximately 6.3 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 67.8 places temporalio/temporal-worker-controller in the A tier.
The external contributor pull request merge rate for temporalio/temporal-worker-controller is 74.0%, based on public PR activity from non-core contributors.
temporalio/temporal-worker-controller does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in temporalio/temporal-worker-controller. Prompt code reviews with positive guidance for new contributors.
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/temporalio/temporal-worker-controller?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (92% approval). Large PRs (>500 lines) take ~30 hours (33% approval). Keep your diff compact for rapid review.
·> make test-integration test -s /home/jaypipes/src/github.com/temporalio/temporal-worker-controller/bin/controller-gen && /home/jaypipes/src/github.com/temporalio/temporal-worker-controller/bin/controller-gen --version | grep -q v0.19.0 || \ GOBIN=/home/jaypipes/src/github.com/temporalio/temporal-worker-controller/bin go install sigs.k8s.io/controller-tools/cmd/[email protected] GOWORK=off GO111MODULE=on /home/jaypipes/src/github.com/temporalio/temporal-worker-controller/bin/controller-gen rbac:roleName=manager-role crd:allowDangerousTypes=true,maxDescLen=0,generateEmbeddedObjectMeta=true paths=./api/... paths=./internal/... paths=./cmd/... \ output:crd:artifacts:config=helm/temporal-worker-controller-crds/templates python3 hack/sync-rbac-rules.py Synced RBAC rules from config/rbac/role.yaml → helm/temporal-worker-controller/templates/rbac.yaml GOWORK=off GO111MODULE=on /home/jaypipes/src/github.com/temporalio/temporal-worker-controller/bin/controller-gen object:headerFile
Is your feature request related to a problem? Please describe. We run a self-hosted Temporal Server and use WorkerResourceTemplate to create one HPA per worker version, using the Temporal Server's approximate_backlog_count metric through Datadog. The Temporal Server already exports worker_version on the backlog metric. However, the controller injects only temporal_worker_deployment_name, temporal_worker_build_id, and temporal_namespace. We currently rename the server's separate deployment/build labels in the collector to match those selectors. Describe the solution you'd like Ideally, metric selector injection should be configurable, so Temporal Worker Controller's users can choose the label names and how their values are derived from the worker deployment, build ID, and Temporal namespace. Supporting worker_version is our immediate use case, but a general configuration mechanism would also accommodate other collector and metrics-adapter conventions. For our setup, this should provide
Is your feature request related to a problem? Please describe. When deploying the temporal-worker-controller in a Kubernetes cluster behind a corporate proxy, there is currently no way to inject environment variables such as HTTP_PROXY, HTTPS_PROXY, and NO_PROXY into the manager container via the Helm chart. The Go runtime, gRPC (used by the Temporal SDK), and net/http (used by controller-runtime / client-go) all natively respect the standard proxy environment variables. However, the Helm chart does not expose an extraEnv (or similar) field in values.yaml, making it impossible to pass these variables without forking or patching the chart. Describe the solution you'd like Add an extraEnv field to values.yaml that allows users to inject arbitrary environment variables into the manager container. This is a common pattern in Helm charts. Example Usage : extraEnv: - name: HTTP_PROXY value: "http://proxy.corp.example.com:8080" - name: HTTPS_PROXY value: "http://proxy.corp.example
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 temporalio/temporal-worker-controller, 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 temporalio/temporal-worker-controller acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.0% were successfully merged into the primary branch.
temporalio/temporal-worker-controller has a recorded first-timer success rate of 72.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 67.8 places temporalio/temporal-worker-controller in the Welcoming tier.
The external pull request merge rate is 74.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
temporalio/temporal-worker-controller does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for temporalio/temporal-worker-controller 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.