feat(gh-copilot): ingest AI adoption phases/cohorts and expose them in Copilot dashboards

[ewega]

Summary

GitHub Copilot usage metrics now include AI adoption phase/cohort data. DevLake’s gh-copilot plugin and Copilot dashboards currently don’t ingest or visualize this dimension, so we can’t track adoption maturity across cohorts.

Problem

Current ingestion and dashboards cover activity/acceptance/PR metrics but miss:

• aggregate phase cohorts (totals_by_ai_adoption_phase) from org/enterprise daily reports
• per-user phase assignment (ai_adoption_phase) from user daily reports

This blocks cohort-based analysis (for example phase progression, engagement by phase, and phase-level productivity signals).

References

• GitHub changelog: 2026-05-29 Copilot usage metrics adds cohorts for AI adoption
  https://github.blog/changelog/2026-05-29-copilot-usage-metrics-api-adds-cohorts-for-ai-adoption/
• copilot-api-schemas/usage-metrics/enterprise-1-day.md (totals_by_ai_adoption_phase)
• copilot-api-schemas/usage-metrics/enterprise-users-1-day.md (ai_adoption_phase)
• copilot-api-schemas/usage-metrics/org-users-1-day.md (ai_adoption_phase)

[ewega]

Proposed scope

1. Plugin ingestion/model

   1. Parse otals_by_ai_adoption_phase from daily aggregate reports (�nterprise-1-day, organization-1-day).
   2. Parse �i_adoption_phase from user daily reports (�nterprise-users-1-day, org-users-1-day).
   3. Add tool-layer persistence:
      • new aggregate phase table (daily, phase grain)
      • phase fields on user daily metrics (or dedicated user-phase table if preferred by maintainers)
   4. Add migration script(s) and register them.
   5. Update e2e fixtures/snapshots for new schema.

2. Dashboards (MySQL + PostgreSQL)

   1. Add phase-aware panels to GitHub Copilot Adoption dashboard:
      • engaged users by phase over time
      • avg interactions / generation / acceptance by phase
      • PR metrics by phase (where available)
   2. Add phase filter variable and wire panel queries.
   3. Preserve existing panels; add cohort views as additive.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.