GitHub connector: support subscribing and unsubscribing to issue notifications
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
Feature request
When GitHub is connected to ChatGPT/Codex, the connector should support managing the authenticated user's notification subscription for an existing GitHub issue.
Specifically, it should be possible to:
- determine whether the current user is subscribed to an issue;
- subscribe to an issue; and
- unsubscribe from an issue.
Motivation
The connector can read issues and perform several issue mutations, but it does not expose an operation for managing issue notification subscriptions.
For example, this request could not be completed through the connected GitHub account:
Subscribe me to
openai/codex#26227andopenai/codex#36650.
The current workaround is to open GitHub manually or fall back to a local GitHub CLI/API workflow. Posting a comment is not an equivalent workaround because it changes the issue discussion and may notify other participants.
Expected behavior
With GitHub connected, ChatGPT/Codex should be able to:
- read the current user's subscription state for one or more issues;
- subscribe or unsubscribe the user as requested;
- read back the resulting state; and
- confirm the result without posting a comment or requiring the user to open GitHub manually.
Acceptance criteria
- The connector can query the current user's subscription state for an issue.
- The connector can subscribe the current user to an issue.
- The connector can unsubscribe the current user from an issue.
- The operations use the connected GitHub identity and permissions.
- Requests involving multiple issues can be completed and confirmed per issue.
- Subscription changes do not post comments or otherwise modify issue content.
- Unsupported or permission-denied operations return a clear, actionable error.
Related issues
- #17475 requests issue creation and a permission-upgrade flow for the GitHub connector. It establishes the broader need for ordinary GitHub mutations through the connector, but does not cover issue notification subscriptions.
- #37583 proposes a separate OpenAI-native feedback tracker with a conversational subscription operation; it does not add subscription support to the GitHub connector.
- #16159 concerns MCP resource-update subscriptions, not GitHub issue notifications.
I could not find an existing issue, discussion, or pull request that requests this specific GitHub connector capability.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the GitHub connector and its existing issue-mutation operations, then trace how connected identity and permissions are handled; done means implementing per-issue subscription status, subscribe, unsubscribe, confirmation, and clear unsupported or permission-denied errors without posting comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100