I’ll start with the first Discussion Copilot helped me create. I’m looking forward to see yours too. ❤️

Not receiving notifications from GitHub Discussions despite correct settings

I’m participating in GitHub Discussions for this repository, but I’m not receiving the notifications I expect, such as replies, mentions, or new topics. This has made it difficult to stay engaged in the community and respond to important conversations promptly.

I’m hoping to find a solution that ensures I, and other community or team members, reliably receive all relevant GitHub Discussions notifications to avoid missing key interactions.

So far, I’ve confirmed that I’m “Watching” the repository, double-checked my notification preferences on the web and via email, and tested across multiple browsers and devices. I’ve also compared my settings with teammates who receive notifications correctly. The issue appears to affect Discussions only; notifications for pull requests and issues are working as expected. I’m using up-to-date versions of Chrome and Firefox, there are no known organization-level restrictions, and some colleagues with similar settings receive all notifications without issue.

Are there any known bugs or limitations affecting Discussions notifications? Are they handled differently from issues and pull requests in terms of timing or criteria? Is there a way to audit missed notifications within GitHub?

If additional details such as screenshots, usernames, or repository information would help, I’m happy to provide them. I’ve already ruled out spam filters and basic configuration issues.

I’d really appreciate clear guidance, tested solutions, or official documentation that can help resolve this. Thanks in advance for any insights.

As a beginner, the most sustainable path is to learn development fundamentals while using AI as a support tool, not a replacement. AI can help you move faster, but without understanding basics like web architecture, data flow, security, and deployment, a marketplace will quickly become hard to maintain or scale. The suggested stack (Next.js, FastAPI, PostgreSQL, AWS) is solid and production‑ready, but it’s too complex as a first step. Start by learning core web concepts and building small projects, then gradually assemble a simplified version of your marketplace. This approach gives you long‑term control, reduces risk, and makes AI genuinely useful instead of fragile magic.

Thank you very much for providing the elaborate answer to the inquiry regarding GitHub’s notification issue.

Some notifications from GitHub Discussions can act differently than other notifications received from GitHub for issues and pull requests; therefore, there are several items that should be checked.

1. Notifications based on participation: Generally, GitHub only sends notifications to you when you participate in a discussion (comment, respond, or get tagged @); therefore, just because you have the repository watched does not guarantee that you will receive notifications for all new discussions or replies.

2. Watch settings that are customized: When watching a repository, your watch settings must be set to “All Activity,” not “Participating and @mentions”. To verify this, go to the repository page and click on Watch → Custom → Discussions (and/or verify that Discussions is enabled).

3. Subscription to specific discussion categories: GitHub provides different categories for Discussions in some repositories; therefore, if the repository has categories, the notifications you receive from GitHub may depend on whether you are subscribed to any categories.

4. GitHub notification filters: Sometimes you will see notifications appear but are filtered out in the GitHub Notifications area; therefore, it’s a good idea to check your GitHub Notifications here:

https://github.com/notifications

5. Check the notification filters (Saved, Participating, or Mentions).

6. Email notifications vs. Web notifications: Your web notifications could be getting delayed or your email notifications could be getting delayed due to the email notification settings in your account, listed as follows:

Account settings → Notifications → Email Preferences.

I hope this information was useful in resolving your issue.

A good way to ensure answers stand out is by using the built in "Mark as answer" feature consistently. Once a reply is marked, GitHub highlights it, making it easier for others to find the solution quickly.
You can also improve visibility by structuring replies clearly:
Start with a direct answer
Add explanation below
Include examples if needed
Another effective method is to edit the original post and include a short summary pointing to the correct answer. This helps future readers without scrolling through the entire thread.

You should keep the original Question as a Question rather than creating a duplicate Product Feedback post immediately.

Since the original thread has now established that the feature doesn’t exist, you can edit the discussion to clearly state the feature request and its use case. If the community category supports answers, the discussion author can also mark the most helpful reply as the answer once the question itself has been resolved. GitHub specifically allows discussion authors to mark answers in answerable categories.

If the goal is to formally submit the feature request to GitHub’s Product team, however, a separate Product Feedback discussion is the cleaner option. GitHub recommends checking for existing feedback first, then adding your use case to an existing thread or creating a new feedback discussion in the relevant product category. Those categories are monitored by the respective GitHub teams.

This keeps the original Q&A useful while giving the feature request the correct feedback channel, without mixing two different purposes in one discussion.