Thank you for picking up the issue.

1. I noticed that generated links to PRs would display the word issues rather than pull.

❯ bin/gh pr view '#8' -wR cli/cli
Opening github.com/cli/cli/pull/8 in your browser.

❯ bin/gh issue view '#8' -wR cli/cli
Opening github.com/cli/cli/pull/8 in your browser.

❯ bin/gh browse '#8' -wR cli/cli
Opening github.com/cli/cli/issues/8 in your browser.

❯ bin/gh browse '#8' -wR cli/cli -n
https://github.com/cli/cli/issues/8

2. quotation marks are missing from the examples with the hashtag? Without goose bumps, it would not generate the correct link for me.

  $ gh browse 217
  #=> Open issue or pull request 217

  $ gh browse #217
  #=> Open issue or pull request 217

❯ bin/gh browse #217
Opening github.com/cli/cli in your browser.

❯ bin/gh browse '#217'
Opening github.com/cli/cli/issues/217 in your browser.

About issues/pull url, I think GitHub will redirect to the correct link anyway. Not sure if I should change this behavior.

In this PR, I just handle the leading # in the argument so gh issue view '#8' -wR cli/cli and gh browse '#8' -R cli/cli will eventually open the same issue/pull request on a browser. I didn't change the parsing logic of browse command.

I think I need an opinion from the team.