Add GitHub Copilot metrics plugin with Grafana dashboards

[Copilot]

⚠️ Pre Checklist

• I have read through the Contributing Documentation.
• I have added relevant tests.
• I have added relevant documentation.
• I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary

Implements a new plugin to collect and visualize GitHub Copilot usage metrics. The plugin follows DevLake's three-layer architecture (raw → tool → domain) and provides two Grafana dashboards for analyzing acceptance rates, user engagement, and editor/language distribution.

Plugin Components (backend/plugins/github_copilot/):

• Models: Connection, Organization (scope), ScopeConfig, Usage (daily metrics with JSON breakdowns)
• Tasks: API collector for /orgs/{org}/copilot/usage endpoint, extractor for JSON parsing
• API: Blueprint generation for pipeline integration
• Migrations: Initial schema with versioned migration scripts

Dashboards (grafana/dashboards/):

• GitHubCopilotMetrics.json: Overview with stat cards (acceptance rate, engaged users, lines accepted) and trend charts
• GitHubCopilotDistribution.json: Editor/language distribution with percentage calculations in SQL

Data Collected:

• Seats, active/engaged users, suggestions/acceptances, lines suggested/accepted
• Chat usage (active users, sessions)
• Language and editor breakdowns (stored as JSON for flexible querying)

Specification (specs/001-copilot-metrics-plugin/):

• Architecture documentation with API integration details
• Phased implementation plan (7 phases)
• Implementation summary tracking completed/remaining work

Screenshots

N/A - Backend plugin implementation

Other Information

Build Status: Plugin compiles successfully to .so (46MB)

Remaining Work:

• Phase 6: UI integration (connection form, scope selection in config-ui)
• Phase 7: E2E tests with CSV fixtures, integration testing
• Phase 8: Performance/security review

Technical Notes:

• Uses helper.NewApiCollector pattern for stateless collection
• Subtask dependencies: CollectUsage → ExtractUsage
• Table naming: _tool_github_copilot_* following plugin conventions
• Registered in table_info_test.go for schema validation

Original prompt

Start the implementation in phases

The user has attached the following file paths as relevant context:

• AGENTS.md

[Chronological Review: The conversation began with the user requesting to create additional tasks for the GitHub Copilot Grafana Dashboard based on a prompt file. The user specified three tasks involving metrics and UI changes. The user later clarified a preference for adding new tasks rather than editing existing ones.]

[Intent Mapping:

1. "I want to create a few additional tasks for the GitHub Copilot Grafana Dashboard." - User's primary request to add tasks.
2. "I'd rather you just add net new tasks rather than edit the existing ones please." - User's clarification to focus on new tasks only.]

[Technical Inventory:

• Repository: apache/incubator-devlake
• Current Branch: 001-copilot-metrics-plugin
• Active Pull Request: GitHub Copilot Metrics Plugin (GitHub Copilot Metrics Plugin apache/incubator-devlake#8674)
• Task Requirements: Metrics for acceptance rate, engaged users, UI modifications, and renaming instances of "Copilot".]

[Code Archaeology:

• Current File: c:\Users\eldrickt\Projects\incubator-devlake\specs\001-copilot-metrics-plugin\tasks.md
• Tasks to be added: Metrics cards, percentage display in dashboards, and renaming conventions.]

[Progress Assessment: User has outlined specific tasks to be added but has not yet completed the addition of these tasks.]

[Context Validation: All necessary context for continuing the task addition is captured, including user preferences and specific requirements.]

[Recent Commands Analysis:

• Last Agent Commands: User requested to create new tasks based on the prompt file and specified preferences for task addition.
• Tool Results Summary: No tool results were generated as the conversation focused on user requests and clarifications.
• Pre-Summary State: The agent was preparing to add new tasks to the specified file when the token budget was exceeded.
• Operation Context: The commands were executed to align with the user's goal of enhancing the GitHub Copilot Grafana Dashboard with new metrics and UI improvements.]

1. Conversation Overview: - Primary Objectives: "I want to create a few additional tasks for the GitHub Copilot Grafana Dashboard." The user aims to enhance the dashboard with specific metrics and UI changes. - Session Context: The user initially requested new tasks, specified metrics to be displayed, and later clarified the need to add new tasks instead of editing existing ones. - User Intent Evolution: The user shifted from a general request for task creation to a more specific focus on adding new tasks without modifying existing ones.

2. Technical Foundation:

• Repository: apache/incubator-devlake
• Current Branch: 001-copilot-metrics-plugin
• Active Pull Request: GitHub Copilot Metrics Plugin (GitHub Copilot Metrics Plugin apache/incubator-devlake#8674)

3. Codebase Status:

• File Name: tasks.md
• Purpose: To document tasks related to the GitHub Copilot Grafana Dashboard.
• Current State: User has outlined tasks to be added but has not yet completed the addition.
• Key Code Segments: Tasks related to metrics and UI changes.
• Dependencies: Relates to the overall functionality of the GitHub Copilot Grafana Dashboard.

4. Problem Resolution:

• Issues Encountered: None explicitly stated, but the user clarified preferences for task addition.
• Solutions Implemented: User's requests for task specifications.
• Debugging Context: No ongoing troubleshooting mentioned.
• Lessons Learned: User prefers to add new tasks rather than modify existing ones.

5. Progress Tracking:

• Completed Tasks: None yet, as the user has only outlined tasks.
• Partially Complete Work: Tasks are specified but not yet added to the file.
• Validated Outcomes: No features confirmed working yet.

6. Active Work State:

• Current Focus: Adding new tasks for the GitHub Copilot Grafana Dashboard.
• Recent Context: User specified tasks involving metrics and UI changes.
• Working Code: The user is working on the tasks.md file.
• Immediate Context: User was preparing to add new tasks when the token budget was exceeded.

7. Recent Operations:

• Last Agent Commands: User requested to create new tasks based on the prompt file and specified preferences for task addition.
• Tool Results Summary: No tool results were generated as the conversation focused on user requests and clarifications.
• Pre-Summary State: The agent was preparing to add new tasks to the specified file.
• Operation Context: The commands were executed to align with the user's goal of enhancing the GitHub Copilot Grafana Dashboard.

8. Continuation Plan:

• Pending Task 1: Add tasks for average acceptance rate and engaged users metrics.
• Pending Task 2: Modify the Editor distribution dashboard to show percentages.
• Priority Information: Focus on adding new tasks as specified by the user.
• Next Action: Proceed to add the outlined tasks to tasks.md as per user specifications...

Created from VS Code.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.