Recent GitClear Improvements
Get your own free automated changelog at the link
By Code Domain
The types of code that have generated the most Diff Delta
tl;dr Summary
September 28, 2026
- Add LLM-backed Diff Digest for PR questions and implement concurrent rebase to permit concurrent repo resumes
September 27, 2026
- Polish updated "New task" popup for mobile
September 23, 2026
- Add LlmWorkContext support to AI telemetry processing and usage metrics
September 21, 2026
- Add v1 Diff Viewer content page; Update WarehouseWriter to adapt batch size for faster CodeLine merges
- Add commit-title overlay rules and layout constants; refactor husk stats rendering
September 19, 2026
- Add group drag-and-drop targets and polish group UI; show Snap image in hover tooltip
September 18, 2026
- Add WelcomeSeriesAnalyzer and refresh welcome mailer to surface AI-relevant metrics
- Add Open Repo context support to PullRequestsController to render public PR pages
- Add changelog image preview to hovered commit tooltip
September 17, 2026
- Add repo_path/repo_slug/workspace_root to telemetry repo derivation and allow restricting LLM fingerprint processing to a repo
- Update commit group progress to broadcast detailed per-stage and per-file build status
- Add runbook: Production job logs — how to find and grep ActiveJob logs to diagnose failing jobs
September 16, 2026
- Add Databricks processing options page and demo components; plan deterministic Silver keys and per-team processing
September 15, 2026
- Add enterprise install script; implement Portkey request interpreters (Phases 1–3) and Docker resource bounding
September 14, 2026
- Migrate Suggested Features leaderboard from Amplenote and implement Portkey request interpreters with improved telemetry parsing
- Add group-husk overlay: render commit-group titles and stats with diagnostics
- Revise group husk labels for readability and hide covered commit titles
September 9, 2026
- Add LLM-authored diff delta and preload; Fix diff reporting in CommitCodeFile concerns
September 8, 2026
- Export CodeLine/CodeLineBodyChecksum/CodeFile and persist repos/orgs to Databricks to retain LLM attribution
- Add reviewContext handling and pollQuestionUrl to data-interrogator UI
Add CommitDefaultBranchConfirmer job to redundantly mark commits as present in default (main) branch
Extracted default-branch inclusion logic from CommitCompleteJob into a new CommitDefaultBranchConfirmer job (app/jobs/commit_default_branch_confirmer.rb) and added denormalization hooks in CommitSite to invoke it when a commit site has kin on the default branch. This adds a redundant call site to improve reliability of marking commits as present in the main/default branch.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add Test Delta & Copy/Paste cohorts to AI Cohort stats; fix and update chart color palette
Adds "Test Delta Cohorts" and "Copy/Paste Cohorts" to the AI Cohort stats lineup and refreshes the chart color palette. Fixes palette retrieval in area-chart-segment-colors.js so AreaChart no longer depends on a missing segment prop (derives palette from chartDataPath), preventing incorrect or missing series colors. Result: new cohort options appear and charts render with consistent colors.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Transform 'Commit count per AI Cohort' to 'Commit Count per Count in AI Cohort' (UI label)
Renamed the UI/stat label from "Commit count per AI Cohort" to "Commit Count per Count in AI Cohort" across the stats view and related presenters/helpers (notably app/views/shared/resource_actions/ai_cohorts_stats.html.haml, presenters and defines). These find-and-replace updates standardize phrasing so cohort commit metrics display a clearer, corrected label in the UI.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Rework repo_import_redirect_path to prioritize GK redirect when no evidence of completion (except usage profile)
Rework the redirect decision logic in the repo import flow so that, when there is no evidence that a user has completed the GK redirect, the GK redirect path takes precedence over other redirect types (except the usage/profile path). This change touches app/lib/controller_concerns/repo_import_concern.rb and app/lib/git_kraken.rb, adjusting the priority rules and how completion evidence is evaluated. Benefit: more predictable, correct redirects when GK completion is uncertain, reducing incorre...
Deployed November 2025
Worked October 2025 in gitclear/kraken
100 Δ
Refactor: Extract GitKraken redirect into its own KrakenControllerConcern for importable usage
Consolidates the GitKraken redirect logic from UserUsageProfilesController into a new app/lib/controller_concerns/kraken_controller_concern.rb as KrakenControllerConcern. The moved methods, including notify_gitkraken_and_redirect and confirm_provider_import_with_gitkraken, are now accessible via import or the user usage profile, improving separation of concerns and testability. This modularization enhances reuse and maintainability of the GK redirect behavior.
Deployed November 2025
Worked October 2025 in gitclear/kraken
100 Δ
Fix fetching missing GitHub remote ID via GraphQL; move CaptureCommitterDetail to post-work (ProcessCommit/ClosedPR)
Moved CaptureCommitterDetail out of the committer callback and into a post-work method invoked by ProcessCommit and ClosedPR, and added Committer#capture_provider_id_if_applicable to fetch missing GitHub provider IDs via GraphQL. Tests for fetching missing remote IDs now pass. May later call the same post-work after PR review creation. Impact: more reliable retrieval of missing GitHub IDs for accurate commit/PR attribution.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add default_branch_processed_back_through to import_progress to indicate how far back default-branch import processed
Return a new default_branch_processed_back_through column on import_progress so callers can determine how far back the default-branch import has progressed. Changes touch RepoConcerns::ImportProgress and RepoImportProgress and update the API reference partial/helper to expose the field. Improves accuracy of import status reporting and simplifies progress/resume logic.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Ensure commits in closed PRs are on default branch; add job logic and tests
Verify that commits participating in a closed pull request are on the repository default branch. Adds checks in ProcessClosedPullRequest (ensure_merged_commits_on_default_branch), updates CommitSite.kin_on_default_branch?, and expands ProcessClosedPullRequest tests. Prevents processing or attributing commits that were merged outside the default branch, improving accuracy of merged-commit handling.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add provider_email to developer_list; fall back to email lookup when git_provider_id doesn't match
Add provider_email to the developer_list JSON and update lookup logic to fall back to matching developers by email when the supplied git_provider_id does not match any known developer. Changes touch developer_list serialization and API helper/ controller logic so responses include provider_email and developers are resolved more reliably, reducing failed or incomplete developer records in API responses.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add teammates_review_minutes stat and LlmTeamCohortStat; move date validation out of StatCacheConcerns
Adds a new teammates_review_minutes committer_stat and LlmTeamCohortStat cohort-building to measure teammates' review minutes and assess whether AI increases review burden. Extracts start_date and date_type_em validation from StatCacheConcerns into a standalone concern since AI stat models don't use digests. Deployed to production Oct 22, 2025 — enables team-level review-time metrics for monitoring AI impact.
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add "remove_repo_paths" to complement "repo_paths" of team API
Pull request
closed
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add passing test to process Copilot stats for Bitbucket/GitLab/Azure organizations
Added a unit test (vendor/gems/llm_metrics/test/unit/github_copilot_different_entity_test.rb) and a VCR cassette to validate processing of Copilot stats from Bitbucket, GitLab and Azure organizations, plus minor updates to app/models/provider_resource_mirror.rb. This targets IN-1 (list developers endpoint returned duplicates) by exercising different-entity handling and improves reliability of stats aggregation in production.
Pull request
merged
Deployed October 2025
Worked October 2025 in gitclear/gitclear
100 Δ
Add test to verify Copilot stats processing for Bitbucket/Gitlab/Azure organizations
Added a test to verify that Copilot stats can be processed for Bitbucket, Gitlab, and Azure organizations. The test exercises the processing path end-to-end and passes in CI, giving greater confidence against regressions. No specific application files are indicated as changed, so the update appears to focus on test coverage. Impact: improves reliability of Copilot stats processing across these providers and reduces risk of regression in production.
Pull request
closed
Deployed October 2025
Worked October 2025 in gitclear/kraken
100 Δ