Closed jdaltonchilders closed 6 years ago
Is this still an open issue? If so can you do the following (pulled from contributing guidelines with your next update?
- Verify if your problem is already solved on the latest version
- Search for open issues before opening a new one
- Specify what version you're using gh --version
- Print the output of npm list -g --depth=0 | grep gh
- Try the command that failed with --verbose to print debugging messages
- Report the exit code of the gh process: echo $? after termination
Thank you!
@jdaltonchilders This is no longer an issue. Please let me know if you are still running into this :smile:
When I run the
gh pr
command inside of a repo I get the following: