cli: Feedback issue for bugs & inconsistencies with GitHub CLI
This is an issue to collect feedback about things that may not be working correctly or as expected with GitHub CLI. It’s not a place for feature requests, as we’d like our primary product feedback to be from users outside of GitHub. Additionally, this repository will likely become public so please don’t share any internally confidential information about upcoming GitHub things in here. Thanks!
To download GitHub CLI for macOS, run brew install github/gh/gh in your Terminal.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (12 by maintainers)
Commits related to this issue
- Merge pull request #66 from github/jg/multiple-ports Multiple ports support in port forwarding — committed to cli/cli by josebalius 3 years ago
Hi friends 👋 I got a similar panic to @shawnbot running
gh pr statuson http://github.com/github/ce-stardust:panic: unsupported status: ""seems like the bad part here 😅@shawnbot @joshaber: Sorry about the crash! It’s since been fixed:
brew upgrade gh@leereilly @tierninho: Much appreciated 🙇
This is great!! I ran into one problem listing statuses for https://github.com/github/github/pull/127437:
I’m going to close this now since we’re using individual issues to catalog things that come up now.
@seejohnrun thanks for trying it out!
gh pr listwill show you all open PRs in a repo (up to 30). You should trygh pr statusit might be closer to what you’re looking for 😄. If there’s language you think would clarify all this would love to hear suggestions!I’d also love a way to get a list similar to
/pullsor just my created or assigned PRs ❤️👋 Just trying this out - I was a bit confused by
gh pr listwhich seems to contain a bunch of PRs I’ve never seen before. Maybe it’s worth adding a note about what this list contains in the output?@tierninho The “recent” section of issue status output right now only displays issues that were created or updated within last 24h. I think that at the time that you were looking at
issue status,#78was already more than a day old. Today it received new labels so it got bumped up to make the list again. We can have a discussion about whether that is correct behavior, but based on current functionality, I don’t think what you’ve seen was a bug.