Skip to content

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

Closed as not planned

Description

@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

Activity

  1. ewega commented on Jun 30, 2026

    @ewega
    ContributorAuthor

    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.
  2. self-assigned this
    on Jun 30, 2026
  3. github-actions commented on Aug 30, 2026

    @github-actions
    Contributor

    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.

  4. github-actions commented on Sep 6, 2026

    @github-actions
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions