Cannot Select or Apply Existing Groups/Lists to Starred Repositories

[suoc]

Select Topic Area

Bug

Body

Description

When attempting to add a newly starred repository to a pre-existing Starred List (Group), the interface fails to display or allow selection of the available lists, making it impossible to categorize the repository immediately upon starring.

This issue significantly hinders organization for users who rely on Starred Lists for categorization.

Steps to Reproduce

Navigate to any unstarred repository (e.g., github.com/microsoft/vscode).

Click the Star button to star the repository. A small popup/toast notification appears immediately after the star is applied.

Click the "Add to list" (or similar grouping/list icon) option within this popup/toast notification.

Expected Result

The popup menu should display a scrollable list of all existing Starred Lists/Groups (e.g., "Web Dev," "ML Tools," "Learning," etc.) with checkboxes, allowing the user to select one or more lists to assign the repository to.

Actual Result

The popup/toast notification appears, but the section intended for selecting lists is empty or fails to load. The user is unable to select or apply any existing Starred List at this point.

(Note: The user can still navigate to their full Starred Repositories page later and add the group manually, but this defeats the purpose of the quick-add function.)

Environment Details

Browser: [e.g., Chrome 120.0, Firefox 119.0, Safari 17.1]

Operating System: [e.g., macOS Ventura, Windows 11, Linux]

Observed Date: [Date you observed the bug, e.g., 2025-11-10]

Thank you for looking into this issue.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[enchained]

Duplicate of https://github.com/orgs/community/discussions/178947

[shinybrightstar]

👋 Welcome to the GitHub Community, @suoc!

Thanks for sharing your Product Feedback. Good news - there's already an active discussion about this topic here: https://github.com/orgs/community/discussions/179124

Please feel free to join that conversation and add your perspective. This helps keep similar discussions together so everyone can benefit from the collective knowledge!

Happy to have you here! 🚀