GitHub Discussions Discovery Enhancement

[bradygaster]

Overview

Extend existing GitHubSourceAdapter to include GitHub Discussions from dotnet/aspire repository. Provides official community feedback, design decisions, and Q&A signals — currently missing from ACCES.

Background

Per gap analysis:

• Current state: ACCES tracks GitHub issues/PRs but ignores Discussions (10-30 discussions/week)
• GitHub Discussions value: Official feedback, feature requests, design debates, community Q&A
• Quick win: Extend existing GitHubSourceAdapter (already has Octokit auth)
• Signal types: Community questions, official announcements, design decisions

Requirements

• Extend GitHubSourceAdapter to query GitHub Discussions API
• Use Octokit GraphQL client (already installed): query dotnet/aspire discussions
• Extract: discussion title, author, URL, category, upvotes, comment count, creation date, body
• Map to ContentItem type with channel="github-discussions", source="github"
• Filter: Only discussions created in last 30 days (configurable)
• Add metadata: { category: string, upvotes: number, commentCount: number, isAnswered: boolean }\
• Respect GitHub API rate limits (5,000/hour authenticated via GITHUB_TOKEN)
• Combine discussions + issues/PRs results in single GitHubSourceAdapter.discover() call

Squad SDK Integration

• Adapter extension: Modify existing GitHubSourceAdapter (no new adapter needed)
• Validation logic: Reuse existing GITHUB_TOKEN validation
• Unified output: Single DiscoveryResult containing issues, PRs, and discussions

Acceptance Criteria

• AC1: GitHubSourceAdapter discovers 5+ dotnet/aspire discussions per run (last 30 days)
• AC2: Each discussion maps to ContentItem with: id, title, url, author, publishedAt, category, upvotes, commentCount
• AC3: Discussions appear in reports with channel="github-discussions" (distinct from "github-issues")
• AC4: If Discussions API fails, issues/PRs discovery continues (partial success)
• AC5: Answered discussions flagged via \isAnswered: true\ metadata
• AC6: No new dependencies added (use existing @octokit/rest or @octokit/graphql)

Dependencies

Depends on: Issue #1 (Architecture Refactor) — GitHubSourceAdapter must exist first

Assigned To

• Bunk (Community scout, GitHub API experience)

Estimated Effort

0.5 sessions

• Add GraphQL query for discussions
• Map discussion data to ContentItem
• Test with dotnet/aspire repo

[github-actions]

🏗️ Squad Triage — Freamon (Lead / Editor-in-Chief)

Issue: #4 — GitHub Discussions Discovery Enhancement
Assigned to: Freamon (Lead / Editor-in-Chief)
Reason: No specific domain match — assigned to Lead for further analysis

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Team roster:

• Freamon (Lead / Editor-in-Chief) → label: squad:freamon
• McNulty (TypeScript Implementer) → label: squad:mcnulty
• Kima (Source Scout (Content)) → label: squad:kima
• Bunk (Source Scout (Community)) → label: squad:bunk
• Omar (Signal Analyst) → label: squad:omar
• Bubbles (Taxonomy + Dedupe Librarian) → label: squad:bubbles
• Daniels (Copilot SDK Specialist) → label: squad:daniels
• Stringer (Squad SDK Orchestrator) → label: squad:stringer
• Ralph (Work Monitor) → label: squad:ralph
• @copilot (Coding Agent) → label: squad:copilot

To reassign, remove the current squad:* label and add the correct one.

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: Freamon (Lead / Editor-in-Chief)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: Freamon (Lead / Editor-in-Chief)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.

[github-actions]

🔄 Ralph — Auto-Triage

Assigned to: Freamon (Lead / Editor-in-Chief)
Reason: No domain match — routed to Lead

Ralph auto-triaged this issue via the squad heartbeat. To reassign, swap the squad:* label.