Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues cannot have more than 100 labels #115

Closed
Nuru opened this issue Nov 22, 2020 · 2 comments
Closed

Issues cannot have more than 100 labels #115

Nuru opened this issue Nov 22, 2020 · 2 comments
Labels
stale The issue has been open for a year without any activity

Comments

@Nuru
Copy link

Nuru commented Nov 22, 2020

I have auto-labeler set up on a monorepo and sometimes it generates (per configuration) more than 100 labels. However, it then fails with the error:

HttpError: Validation Failed. Issues cannot have more than 100 labels: 

There needs to be some mechanism to handle the case when it would generate more than 100 labels. Ideas:

  • Some way to truncate the list (and perhaps add a "truncated" label)
  • A way to prioritize labels, so that the most important labels are set even if some others are truncated
  • Some way to merge labels if there are too many
  • An alternative label configuration to use if the first one generates too many labels.
@MaksimZhukov
Copy link
Contributor

Hello @Nuru !
This issue has been open for a year without any activity, so I'm going to close it as stale.
Please feel free to contact us if the issue is still relevant to you and we will reopen it.
Thanks!

@MaksimZhukov MaksimZhukov added the stale The issue has been open for a year without any activity label Dec 12, 2022
@radulle
Copy link

radulle commented Jan 4, 2023

As there are more and more mono-repos this issue will come up more and more so it needs to be resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue has been open for a year without any activity
Projects
None yet
Development

No branches or pull requests

3 participants