> Testing the API. I'm trying to understand if, for the GH backend, "comments body" and "issue body" are the same. I mean, considering what I'm looking through the API, they are not.

[iron-eater]

          > Testing the API. I'm trying to understand if, for the GH backend, "comments body" and "issue body" are the same. I mean, considering what I'm looking through the API, they are not.

234234

Originally posted by @iron-eater in #1347 (comment)

[junzuijifei]

In the context of GitHub's API, "comments body" and "issue body" are not the same.

1. "Issue body": This typically refers to the main description or content of an issue in a GitHub repository. When you create or edit an issue, you can provide a description that explains the problem, feature request, or task in detail. This is the main text associated with the issue.
2. "Comments body": Comments in the context of GitHub refer to the individual responses or messages left on issues, pull requests, or commits. Each comment has its own body or text content, which can be used for discussions, questions, feedback, and so on.
   These two types of content serve different purposes. The "issue body" is the initial description of the issue, while "comments body" are responses and discussions related to that issue. They are distinct and stored separately in the GitHub API.