The gh issue create command fails if multiple labels are specified and there is a space after the comma separating labels

[mrememisaac]

Describe the bug

gh issue create fails if multiple labels are specified and there is a space after the comma separating labels. It expects there should be no space only a comma separating labels. If it finds a space it takes the space to be part of the label and thus fails to create the issue

Affected version

2.4.0+dfsg1 (2022-03-23 Ubuntu 2.4.0+dfsg1-2)

Steps to reproduce the behavior

1. Type this 'h issue create --title "Add Prettier as dev dependency and format script" --body "Add Prettier as a dev dependency and add a format script to standardize project formatting." --label "chore, tooling"
2. View the output 'could not add label: ' tooling' not found'
3. See error

Expected vs actual behavior

Expected: The content of the label flag should be split by comma and then trimmed before being compared with the existing labels list.
Actual: The content are not trimmed, they are used as is.

Logs

Paste the activity from your command line. Redact if needed.

NA

[Ari07092000]

[Ari07092000]

No description provided.

[Ari07092000]

Duplicate of #11260

[babakks]

Thanks for reporting this, @mrememisaac! 🙏

Generally, with a CSV list, the user is not supposed to add whitespace around the delimiters. That's why I'm going to remove the bug Something isn't working label.

Anyway, I checked the API and GUI behaviour to confirm if it's even possible to have labels with leading/trailing whitespaces, and the good news is at the end they're trimmed. So, trimming labels seems to be a non-breaking change. The only issue is gh has a number of commands that accept a list of labels all of which should be fixed:

• issue list/create/edit
• pr list/create/edit
• search issues/prs

To further understand the use case, can you please let me know if this behaviour is blocking you or causing problems at your end?

[github-actions]

Thank you for your issue! We have categorized it as a feature request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.

Unless you see the help wanted Contributions welcome label, we are not currently looking for external contributions for this feature.

If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.