Private and Public Star Lists

[httpanand]

Please add a feature to make Star lists public and private .. It'll be helpful to some users like me . Thank You

[jecastrom]

I agree. The list feature is fantastic. However, I notice the list URL is not public, even being the repo's public. It would be beneficial to have their repos organised and share them, for example, with employers, only a specific list of projects, rather than the profile URL full of projects and people getting lost finding stuff.

[glewe]

+1

[cliffordfajardo]

I also hit the 16 limit limitation quickly.
my use case:

• I typically view my GitHub newsfeed feed and GitHub trending list several times a week and I like to categorize repos i want to experiment with

Before GitHub lists, I created my own lists using an external store (notion database) but the need to context switch out of the GitHub web app to save the repo and categorize it usually caused me to just defer the action 😢 due to the extra step / time needed specially since I use GitHub on mobile a lot (I use it to catch up on updates / view GitHub feed like I do my twitter feed )

Related

• the total allow lists is too small, it's only 16 #8633
• More than 16 lists #9672 (comment)
• Unlimited lists #9513

[melMass]

+1 I had the exact same workflow (notion based) and this feature is making it much better but I hit the limit pretty quickly 😢

[fluteds]

It would be nice if private lists worked like private Gists in that anyone with the link can view it.

[ZelnickB]

It might also be nice to add an option also for private lists like private repositories (you can invite people to view and/or edit the lists)

[junibrosas]

Came here after reaching the 16 limitation. Github's list feature is awesome and very helpful and I slowly migrated my starred repos from an external manager.

[ghost]

+ 1

[telemakhos]

Highly demanded feature and simple to implement. Why is taking so long?

[httpanand]

yeah it'll be very useful for many i guess !

[svengreb]

Sounds like you must be a pure genius and can implement it for “them“ in some days, can‘t you?
Putting the sarcasm aside, please don‘t demand for things without any knowledge about the high complexity of gigantic systems like GitHub or any other kind of global-serving platforms. Changing a single line of code in such systems can have fatal consequences.
Please stop to beg for something and produce non-productive noise in such large threads instead of contributing useful information.

[telemakhos]

Sounds like you're a victim of microservices... 😂 https://www.youtube.com/watch?v=y8OnoxKotPQ

[ooahz]

+1

[ZelnickB]

I support increasing (or removing, if that isn't too much to ask) the 16-list limit and allowing lists to be made private.

[Titlap77]

Please add a feature to make Star lists public and private .. It'll be helpful to some users like me . Thank You

[dotrinh-USE-Inc]

same here

[LiyJessica]

+1

[svengreb]

What does all of this have to do with privacy settings for a single user? These topics you listed have absolutely nothing to do with the topic in this discussion.
This is like saying that you have to make your bank account balance public, otherwise other customers of the bank might feel excluded.
The projects you like are your own opinion and when you don‘t want to share them this should be your own decision.
In fact all your listed points are the absolute opposite of whats important: protecting the privacy of users instead of making them the perfect “glass figure“ everyone can suck information for data collection from.

Allowing to make private lists fits perfectly into features like creating private repositories for, well, the code that is your property.

[yorickshan]

same here

[LiteBrite82]

Hi All!

This discussion is being locked and linked to a single discussion to better track user feedback: Dec 9, 2021 Private List #8626 Please continue any further discussion there.

All data and feedback in this discussion is still being tracked and will be combined (internally) with the above mentioned discussion.

[LiteBrite82]

💬 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. ⭐