Thanks @arohner! We try to keep our issues (as best as possible) organized by units of work that we or someone from the community could pick up, so I'd like to split these two things out as they're a bit different, and also expand the scope of each to issues and pull requests as opposed to just issues. I'm going to edit this one to be scoped to commenting, and if you'd like to make a new issue for editing an existing issue or pull request, you're welcome to do so. Thanks!

+1

+1 for gh issue comment #123

+1 for gh issue comment #123

Nitpick: it would be even better without the # which would introduce plenty of confusions in shell commands.

As a sidenote, the git-hub program already supports this feature so if ghaims at replacing it, it would really be nice and convenient to have this.

(This comment has actually been written with git hub issue comment)

I would ❤️ to have this feature. But I agree with @shindere , it would be better without the #.

without the #

100% agree - the standard convention of gh (and also, hub) is to leave out the # ... Also, since # is the typical shell comment, if used, I'm 99% sure you'd have to escape it. See below.

Relatedly, consider #528 in conjunction with editing - they are two distinct features, but they are related 😁

Compare:

$ echo hello #hello 
hello
$ echo hello \#hello
hello #hello

Also, I might need more coffee ... but I can't find a way to view all of the comments in an issue/PR? It seems to just show the top? (On an interesting side note, hub issue show will happily display both issues/PRs whereas gh issue view will only view issues and not PRs. As I recall, the ID# between the two is unique - i.e. there will never be an issue number 1 and PR number 1 -- If that's the case, I'm not 100% sure what's better, I suppose displaying an error if you run gh issue view <PR#> but you're specifically looking for an issue does serve as validation of which one you're querying... )

On an interesting side note, hub issue show will happily display both issues/PRs whereas gh issue view will only view issues and not PRs. As I recall, the ID# between the two is unique - i.e. there will never be an issue number 1 and PR number 1 -- If that's the case, I'm not 100% sure what's better, I suppose displaying an error if you run gh issue view <PR#> but you're specifically looking for an issue does serve as validation of which one you're querying...

@danieldjewell This is being addressed in #1153 and #1131