📜 Entire CLI hooks into your Git workflow to capture AI agent sessions as you work. Sessions are indexed alongside commits, creating a searchable record of how code was written in your repo.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 66%
Response Time: -
First Timer Success: 53%
entireio/cli has a recorded first-timer success rate of 52.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in entireio/cli respond to incoming external pull requests in approximately 0.0 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 57.2 places entireio/cli in the A tier.
The external contributor pull request merge rate for entireio/cli is 66.4%, based on public PR activity from non-core contributors.
entireio/cli currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (72% critical review signals). Ensure PRs strictly follow guidelines before requesting review in entireio/cli.
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/entireio/cli?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 Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
#2171 isolated the 38 git invocations in cmd/entire/cli/strategy/hooks_test.go by assigning cmd.Env = testutil.GitIsolatedEnv() at each call site. That closed the leak in that file, but by repetition - nothing prevents the 39th call site from omitting it, which is the exact failure #2171 was repairing. Sixteen sibling sites remain unisolated: cmd/entire/cli/review/scope_test.go (6) cmd/entire/cli/gitrepo/gitstatus_guard_test.go (3) cmd/entire/cli/strategy/commit_hook_perf_test.go (3, behind //go:build hookperf) singles in review_context_test.go, integration_test/resume_test.go, checkpoint/redact_cache_scope_test.go, checkpoint/remote/git_test.go Without isolation these read the developer's global gitconfig. #2171 demonstrated the consequence: with init.defaultBranch=feature set globally, four tests in hooks_test.go failed with an opaque failed to create worktree: exit status 255. Suggested: a file-local or package-level runGit(t, dir, args...) helper that bundles the Env assignment a
Follow-up to #1926 (merged as c7a96436). persistentRefLockPath creates a lock file per ref under <git-common-dir>/entire-persistent-ref-locks/ (cmd/entire/cli/checkpoint/persistent_ref_update.go:63). Under the git-refs backend that is one file per checkpoint ref, created on first write and never removed. The MigrateBranchToRefs path creates one for every migrated checkpoint in a single pass. cmd/entire/cli/strategy/cleanup.go has no reference to that directory, so entire clean does not discover or reclaim it. Why this is worse than the existing precedent shadow_ref.go:80-84 uses the same pattern for <git-common-dir>/entire-shadow-locks/, and cleanup.go doesn't know about that one either. The difference is bound: shadow lock files are keyed by base commit and worktree, so the set is bounded by branch activity. Persistent-ref locks are keyed by checkpoint ref, so the set grows monotonically with checkpoint count and never shrinks. Suggested fix Add both lock directories to cleanup discov
Summary Users can see Copilot CLI sessions on the Entire dashboard, and the session logs/files/checkpoints are present, but the session detail view may show: No transcript messages to display. In other cases, the session is only partially visible: tool calls or later turns appear, but the actual conversational text is missing or truncated. This happens because some Copilot transcripts contain empty data.content fields for both user.message and assistant.message, while the real displayable text lives in fallback fields: user.message.data.transformedContent assistant.message.data.reasoningText Impact Copilot sessions are detected and checkpointed correctly, but the most important session details are missing from the UI. That makes the session look broken, blank, or incomplete even though the agent did real work. Observed behavior Session shows up in the sessions tab Files/logs/checkpoints are present Session detail page has no displayable user/assistant messages, or only a partial tra
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 entireio/cli, 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 entireio/cli acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.4% were successfully merged into the primary branch.
entireio/cli has a recorded first-timer success rate of 52.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 57.2 places entireio/cli in the Welcoming tier.
The external pull request merge rate is 66.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, entireio/cli currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for entireio/cli 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.