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

add support to chain the addition/removal of multiple labels to issues #46

Closed
ghuntley opened this issue Jun 27, 2011 · 3 comments
Closed

Comments

@ghuntley
Copy link
Contributor

› ghi label add api security 20
error: label() takes at most 4 arguments (5 given)

› ghi label add api,security 20
error: server problem (HTTP Error 422: Unprocessable Entity)

› ghi label add security 20    
labels for issue #20:
- security

› ghi label add api 20     
labels for issue #20:
- api
- security
@jsmits
Copy link
Owner

jsmits commented Jun 27, 2011

Not sure about which UI to use for this. I had the same problem when "designing" the label UIs, namely: labels in github can contain spaces. I accepted this "flaw" in the UI and so far nobody complained about it. But now, this problem pops up in your first example: should it be regarded as one label ('api security') or as two ('api' and 'security'). Parsing the args in your second example could be even more complex, when there are labels with spaces involved. What do you think? Any suggestions on how to handle this properly?

@ghuntley
Copy link
Contributor Author

Issues separated by commas, whitespace enclosed with "/' or escaped out as per standard unix shell conventions?

i.e.

$ ghi label add api,securtiy,"user interface"

That would all passed through as one {arg}

@jsmits
Copy link
Owner

jsmits commented Jun 28, 2011

Of course ;-) Looks fine to me. I don't have time to implement it myself at the moment, would you care to do it?

@jsmits jsmits closed this as completed Dec 5, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants