Evaluate API support for automated monitoring of GitHub Discussions

[fullsend-ai-triage]

Note

This issue was automatically generated from meeting notes by the scribe agent.
Please review, edit, and add any missing context before prioritizing.

Problem

The team wants to automate monitoring of GitHub Discussions for relevant activity (e.g., security-related conversations, community questions needing attention). Before committing to an implementation, the team needs to verify whether the current GitHub API (REST and/or GraphQL) supports querying Discussions programmatically, including filtering, pagination, and event-based triggers.

Options considered

1. GitHub GraphQL API: The GraphQL API may expose Discussion objects. Need to verify query capabilities, filtering options, and whether webhook events exist for new discussions.
2. GitHub REST API: Check if REST endpoints exist for Discussions or if this is GraphQL-only.
3. Third-party integrations: Evaluate whether existing tools or bots already provide Discussion monitoring capabilities that could be reused.

Acceptance criteria

• Document whether the GitHub API supports querying Discussions (REST, GraphQL, or both)
• Identify available filtering and pagination capabilities for Discussion queries
• Determine if webhook events exist for Discussion creation and updates
• Summarize findings in a brief technical note with a recommendation on feasibility

Related

• Supports the broader security notification workflow discussed alongside Support GitHub Security Advisories #5894
• Source: Meeting notes

[fullsend-ai-triage]

Meeting update — 2026-08-11

Relevant to this issue: The team discussed using GitHub Discussions as a scalable chat interface for agent interactions, directly extending the scope of the API evaluation tracked here.

• The proposal to use GitHub Discussions as an input surface for agents is pending further async review and discussion
• An ADR for conversation surface participation is in progress (PR docs(adr): add ADR 0086 for conversation surface participation #6083)
• The team agreed to evaluate the architecture decision record asynchronously before committing to implementation

Related PRs: PR #6083 — ADR 0086 for conversation surface participation

Next steps: Complete async review of the ADR to determine feasibility and design direction. See also #6081 (broaden Slack notifications for GitHub Discussions).

Meeting notes

[ifireball]

Closing: GitHub Discussions feasibility for Fullsend participation is recorded in ADR 0086 (merged via #6083). Implementation tracking continues in #6402.