Add support for discussion comment

[khiga8]

Fixes: #11

This PR adds support for discussion comments. Because the action.yml is getting big, I introduced a queries.sh file to move the GraphQL calls into, including the mutation call we introduced in #14.

We are using the addDiscussionComment and setting the replyToId to post a comment as a reply in a thread.

When replying to a top-level discussion comment, we're able to use github.event.comment.node_id as the replyToId to post a reply successfully.

However, I ran into issues making the same call when replying to a discussion comment inside of a thread. I kept running into the error:

gh: Parent comment is already in a thread, cannot reply to it

I discovered that replyToId has to be a top-level/parent comment node id. Since the github.event.comment.node_id only contains the node ID of the comment we're replying to, we must make a GraphQL query to get the parent comment node ID. We do that in the function getDiscussionReplyToId.

[accessibility-bot]

👋 Hello and thanks for pinging us! You've entered our first responder queue. An accessibility first responder will review this soon.

• 💻 On PRs for our review: please provide a review environment with steps to validate, screenshots (with alt text), or videos demonstrating functionality we should be checking. This will help speed up our review and feedback cycle.
• ⚠️ If this is urgent, please visit us in #accessibility on Slack and tag the first responder(s) listed in the channel topic.

[kendallgassner]

Is it possible to combine addDiscussionComment and addDiscussionCommentAsReply and just leave replyToId as undefined.

[khiga8]

Done in ad9af45! :)

[kendallgassner]

Sorry! I meant could you do something like this:

if [ -n $REPLY_TO_ID ]; then; else REPLY="$REPLY_TO_ID"; fi
gh api graphql -F discussionId="$DISCUSSION_NODE_ID" -F replyToId=$REPLY -F body="$MESSAGE" -f query='
      mutation($discussionId: ID!, , $replyToId: ID, $body: String!) {
          addDiscussionComment(input: {discussionId: $discussionId, replyToId: $replyToId, body: $body}) {
          comment {
              id
          }
        }
      }
    '

^ I think the var can be passed in as null on graphql

[kendallgassner]

note: the if statement only is used to add "" around REPLY_TO_ID if it is not null.

[khiga8]

Oh I see. I think I tried this before and ran into a GraphQL error. Let me try again to confirm.

[khiga8]

We run into the following error, so I think we need to stick with two separate calls.

gh: Could not resolve to a node with the global id of ''
{"data":{"addDiscussionComment":null},"errors":[{"type":"NOT_FOUND","path":["addDiscussionComment"],"locations":[{"line":3,"column":9}],"message":"Could not resolve to a node with the global id of ''"}]}

[kendallgassner]

Oh weird it auto resolves it to an empty string.

[kendallgassner]

❤️