-
Notifications
You must be signed in to change notification settings - Fork 8k
Closed
Labels
bugSomething isn't workingSomething isn't workingpriority-2Affects more than a few users but doesn't prevent core functionsAffects more than a few users but doesn't prevent core functions
Description
Describe the bug
A clear and concise description of what the bug is. Include version by typing gh --version.
❯ gh --version
gh version 1.14.0 (2021-08-04)
https://github.com/cli/cli/releases/tag/v1.14.0
Steps to reproduce the behavior
- Create a PR on a repo, and also create an issue
- See that the numbers come out in order (1, then 2 etc)
- Try to do:
gh issue comment -b hello 1- You get an error saying:
GraphQL error: Could not resolve to an Issue with the number of 1.
- You get an error saying:
- Try the same thing with
2instead of one and it works fine
Expected vs actual behavior
What was expected is that using the issue API (through the cli) should allow you to post a comment on a PR or an issue (same as the regular github api REST api)
The reason for this is that the action issue_comment on github actions does not tell you if that issue was a pull request or an actual github issue, and we still need to have the ability to post a comment to both without having to run one on error and then switch to using gh pr comment ...
Logs
❯ gh issue comment -b hello 194
GraphQL error: Could not resolve to an Issue with the number of 194.
❯ gh pr comment -b hello 194
https://github.com/serveside/serveside/pull/194#issuecomment-898608949
❯ gh --version
gh version 1.14.0 (2021-08-04)
https://github.com/cli/cli/releases/tag/v1.14.0Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingpriority-2Affects more than a few users but doesn't prevent core functionsAffects more than a few users but doesn't prevent core functions