We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I run gh pr status , I see the following error message and no other output:
gh pr status
graphql error: 'Field 'statusCheckRollup' doesn't exist on type 'Commit', Field 'reviewDecision' doesn't exist on type 'PullRequest''
gh version 0.6.1 (2020-03-04)
I'm not sure what the output of gr pr status should look like, but the error is definitely a sign that something is going wrong.
gr pr status
$ gh pr status graphql error: 'Field 'statusCheckRollup' doesn't exist on type 'Commit', Field 'reviewDecision' doesn't exist on type 'PullRequest''
The text was updated successfully, but these errors were encountered:
@AdamVig Thanks for filing this.
I suspect you are authenticated with a Personal Access Tokens, which renders some commands useless; most notably the gh pr status, like so:
It's better to authenticate on a local machine using OAuth and then copy the resulting ~/.config/gh/config.yml file to the remote machine under SSH.
~/.config/gh/config.yml
Example: #297 (comment)
Sorry, something went wrong.
@tierninho Thank you! gh pr status now works for me. ✨
I am on Windows with WSL, so I followed these steps:
cmd.exe
choco install gh
refreshenv
gh pr list
%USERPROFILE%\.config\gh
config.yml
~/.config/gh
Excellent! Glad you are back in action. Thank you for detailing the steps, as it will be helpful for anyone else who runs into this.
No branches or pull requests
Describe the bug
When I run
gh pr status
, I see the following error message and no other output:gh version 0.6.1 (2020-03-04)
Steps to reproduce the behavior
gh pr status
(in case it matters: on a private repository in a GitHub organization)Expected vs actual behavior
I'm not sure what the output of
gr pr status
should look like, but the error is definitely a sign that something is going wrong.Logs
The text was updated successfully, but these errors were encountered: