GitHub Commit Ingestion Breaking Change

Learn about GitHub Events API changes that started impacting SEI commit ingestion on October 7, 2025.

GitHub introduced a breaking change to the Events API, which Harness SEI relies on to ingest commit activity from connected GitHub repositories.

As of October 7, 2025, GitHub no longer exposes commit details in the payload for relevant event types. Because Harness SEI depends on this data to ingest commits that occur outside of pull requests (PRs), this temporarily prevented Harness SEI from ingesting commits that were not associated with PRs. Harness SEI has implemented a workaround and completed backfills for affected GitHub integrations.

This change affects all Harness SEI customers who integrate with GitHub Cloud or GitHub Enterprise Server.

RESOLVED

Harness SEI has completed backfilling missing non-PR commit data for GitHub integrations affected by the GitHub Events API change. Commits from October 2025 through early January 2026 have been successfully backfilled for all healthy, non-satellite GitHub integrations.

Some integrations still require action before backfill can complete.

Backfill status and pending integrations

Harness SEI has successfully backfilled missing non-PR commit data from October 7, 2025 through January 5, 2026 for all customers whose GitHub integrations meet the following criteria:

• The integration is healthy

• The integration is non-satellite

• The GitHub access token is valid and has sufficient repository access

Backfill is pending for integrations where:

• The GitHub access token has expired

• The token does not have access to all required repositories (for example, some Pearson customer integrations)

• The integration is configured as a satellite integration

Affected customers have been notified through Harness Support. Once tokens or access are updated, Harness SEI will schedule and complete the remaining backfills.

No impact

• Commits associated with PRs: Harness SEI continues to ingest and attribute these commits without any change. For most teams working through PR workflows, SEI data remains unaffected.

Commit types no longer ingested (historical)

Between October 7, 2025 and January 5, 2026, the following commit types were temporarily missing from Harness SEI:

• Direct commits pushed to branches without a PR

• Feature-branch commits that never went through a PR

• Any commit not linked to a PR during the affected window

These commits have now been backfilled for eligible integrations.

IMPACT SCOPE

Based on internal analysis, the scope of this impact is fairly small. The commit types listed above account for a small fraction of overall commit volume across customers (approximately 3.17%). During the affected window, the limited number of missing commits was expected to have minimal impact on metrics.

Affected SEI metrics and widgets

The following metrics and widgets were impacted during the affected window only. Backfilled data is now reflected for eligible integrations.

SEI Version	Impacted Metrics and Widgets
SEI	- SCM Commits Report - SCM Commits (Single Stat) - SCM Rework Report - Trellis (Individual Raw Stats) - Trellis Scores - SCM Coding Days Report - SCM Coding Days (Single Stat) - SCM Committers Report
AIDI	- DORA (Lead Time for Changes): commit-based correlations may be incomplete - Coding Days metrics - Code Rework

FAQs

Has the GitHub commit ingestion issue been resolved?

Yes. Harness SEI has completed backfills for missing non-PR commits from October 2025 to January 5, 2026 for all healthy, non-satellite integrations. Some integrations may still require token updates before backfill can complete.

If GitHub says there is no loss of data, why is Harness SEI missing some commits?

GitHub has removed commit-level details from the Events API payloads and now requires customers to retrieve those details separately using the REST API. SEI’s current ingestion pipeline relies on Events API payload completeness to ingest non-PR commits efficiently at scale.

While the data still exists in GitHub, retrieving it now requires additional API calls, which introduces architectural, rate-limit, and latency considerations that Harness is actively evaluating.

Why are commits associated with Pull Requests not affected?

Pull Request APIs continue to expose full commit metadata directly. Harness SEI already ingests PR-linked commits through these APIs, so those commits and related metrics remain fully intact and unaffected by this change.

Does this mean historical commit data will be lost or removed?

No. Historical commit data prior to October 7, 2025 remains unchanged and available in Harness SEI. This change only affects the ingestion of new non-PR commits after the GitHub enforcement date.

What impact can we expect to see on our metrics?

Across our customer base, non-PR commits represent approximately 3.17% of total commit volume. Actual impact may vary depending on your team’s development workflow.

Teams that frequently push commits directly to branches without PRs may see a higher relative impact.

Will Harness SEI backfill missing commit data once a solution is identified?

The Harness SEI Engineering team is evaluating potential ingestion approaches. Whether historical backfill will be possible depends on the final technical solution and GitHub platform constraints.

Where will updates be shared?

This page will be updated as the Harness SEI Engineering team completes its evaluation or as additional guidance becomes available from GitHub.