[Feature Request] Please Allow More Than 32 Lists! 🙏

[eshack94]

Select Topic Area

Product Feedback / Feature Request

Body

Huge fan of the new lists feature, however I like my lists to be quite granular and as such I find myself needing more than 25 32 lists.

Can you please allow us to have more than ~~25~ 32 lists? Maybe 50 or 100?

Edit: Correction. Currently only 32 lists are allowed (initially I said 25).

[linuxlawson]

You can have 32 😄

[taska2]

Thank u

[marktops]

Done ✅

[ygxxii]

I had to delete a lot lists that not using "currently". Sad.

[anasaboayham]

🥲🥲🥲

[Mo99411]

Ok

[eshack94]

Bump! is this something that can be considered?

[anasaboayham]

Ya

[anasaboayham]

Account problems can be resolved

[mofosyne]

Would be better if we could basically do hashtags of repos

[RSS1102]

yes,After star and list, I want to give him a label of my own to annotate his role.

[dmarx]

I use lists to organize newly released AI research. I've been at "list capacity" for months and new research streams are emerging practically every month. re-allocating content between lists to try to deprecate old lists to create new ones is a silly requirement. The 32 lists constraint is arbitrary, PLEASE let us make more lists or come up with a more free-form solution like letting users add tags or comments to their stars.

[segyges]

I don't use lists but have @dmarx as an upstream dependency for my ability to keep on top of stuff.

[lilpacy]

I've been waiting for this for a long time.　　
I'd like to be able to put more than one in one as a tag rather than a category 😊

[eshack94]

Bump. Can someone “in the know” at GitHub please respond? Feels like we’re talking to the void here.

Lists is an excellent feature. However its current utility/usefulness is heavily handicapped by the number of lists being arbitrarily capped at 32.

Just trying to understand better:

• Is it an intentional decision to leave the number of lists capped at 32?
  • If so, is there some technical/cost/performance constraint associated with increasing the list count at scale?
• Or, has increasing allowed lists just not had time/resources to be prioritized?
• Or, have folks responsible for the initial development of the feature left the company and no one left knows how to extend the existing code?
• Or, something else?

If you all aren’t not willing to prioritize this, or if there’s some technical/cost/performance constraint preventing it, can someone at GitHub please just say so, so that it’s clear?

Is there a preferred/official way to submit a feature request outside of these forums so that it’s tracked and prioritized internally?

Side-rant (respectfully):

This discussion was created in good faith (aiming to help you all improve the feature) on February 9th, 2023, almost a year ago. In that time, no one from GitHub has replied.

The lack of a response from someone at GitHub (someone actually informed about the Lists feature, like a TPM or someone else) makes it feel like these discussion boards are actually completely ignored by GitHub and just a way to help GitHub users feel “heard” (by other users).

Makes it seem like the company doesn’t care too much about improving an otherwise promising feature.

Even an answer from an informed GitHub employee like “No, we can’t do that.” would be greatly appreciated. The lack of info, transparency, and communication on these forums is disheartening. 😢