You can have 32 😄

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

Bump! is this something that can be considered?

Would be better if we could basically do hashtags of repos

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.

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?