Maybe it's just me but I was confused for a second that /hosts foo bar didn't do what I expected (set target hosts to foo and bar), it just listed the current targets.
I realised it's because I meant /host, and /hosts is an alias for /targets.
Maybe it would be slightly clearer if /targets bails if any arguments are provided, because it doesn't seem like it really looks at them.
Maybe it's just me but I was confused for a second that `/hosts foo bar` didn't do what I expected (set target hosts to `foo` and `bar`), it just listed the current targets.
I realised it's because I meant `/host`, and `/hosts` is an alias for `/targets`.
Maybe it would be slightly clearer if `/targets` bails if any arguments are provided, because it doesn't seem like it really looks at them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Maybe it's just me but I was confused for a second that
/hosts foo bardidn't do what I expected (set target hosts tofooandbar), it just listed the current targets.I realised it's because I meant
/host, and/hostsis an alias for/targets.Maybe it would be slightly clearer if
/targetsbails if any arguments are provided, because it doesn't seem like it really looks at them.I agree with the second part of this. I think making the host manipulation commands more unambiguous would be helpful.