Create a reaction to a commit comment. A response with a Status: 200 OK
means that you already added the reaction type to this commit comment.
octokit.reactions.createForCommitComment({owner,repo,comment_id,content,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | yes | The reaction type to add to the commit comment. |
See also: GitHub Developer Guide documentation.
Create a reaction to an issue. A response with a Status: 200 OK
means that you already added the reaction type to this issue.
octokit.reactions.createForIssue({owner,repo,issue_number,content,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
issue_number | yes | issue_number parameter |
content | yes | The reaction type to add to the issue. |
See also: GitHub Developer Guide documentation.
Create a reaction to an issue comment. A response with a Status: 200 OK
means that you already added the reaction type to this issue comment.
octokit.reactions.createForIssueComment({owner,repo,comment_id,content,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | yes | The reaction type to add to the issue comment. |
See also: GitHub Developer Guide documentation.
Create a reaction to a pull request review comment. A response with a Status: 200 OK
means that you already added the reaction type to this pull request review comment.
octokit.reactions.createForPullRequestReviewComment({owner,repo,comment_id,content,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | yes | The reaction type to add to the pull request review comment. |
See also: GitHub Developer Guide documentation.
Create a reaction to a team discussion comment. OAuth access tokens require the write:discussion
scope. A response with a Status: 200 OK
means that you already added the reaction type to this team discussion comment.
Note: You can also specify a team by org_id
and team_id
using the route POST /organizations/:org_id/team/:team_id/discussions/:discussion_number/comments/:comment_number/reactions
.
octokit.reactions.createForTeamDiscussionCommentInOrg({org,team_slug,discussion_number,comment_number,content,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
comment_number | yes | |
content | yes | The reaction type to add to the team discussion comment. |
See also: GitHub Developer Guide documentation.
Create a reaction to a team discussion. OAuth access tokens require the write:discussion
scope. A response with a Status: 200 OK
means that you already added the reaction type to this team discussion.
Note: You can also specify a team by org_id
and team_id
using the route POST /organizations/:org_id/team/:team_id/discussions/:discussion_number/reactions
.
octokit.reactions.createForTeamDiscussionInOrg({org,team_slug,discussion_number,content,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
content | yes | The reaction type to add to the team discussion. |
See also: GitHub Developer Guide documentation.
Note: You can also specify a repository by repository_id
using the route DELETE /repositories/:repository_id/comments/:comment_id/reactions/:reaction_id
.
Delete a reaction to a commit comment.
octokit.reactions.deleteForCommitComment({owner,repo,comment_id,reaction_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
Note: You can also specify a repository by repository_id
using the route DELETE /repositories/:repository_id/issues/:issue_number/reactions/:reaction_id
.
Delete a reaction to an issue.
octokit.reactions.deleteForIssue({owner,repo,issue_number,reaction_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
issue_number | yes | issue_number parameter |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
Note: You can also specify a repository by repository_id
using the route DELETE delete /repositories/:repository_id/issues/comments/:comment_id/reactions/:reaction_id
.
Delete a reaction to an issue comment.
octokit.reactions.deleteForIssueComment({owner,repo,comment_id,reaction_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
Note: You can also specify a repository by repository_id
using the route DELETE /repositories/:repository_id/pulls/comments/:comment_id/reactions/:reaction_id.
Delete a reaction to a pull request review comment.
octokit.reactions.deleteForPullRequestComment({owner,repo,comment_id,reaction_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
Note: You can also specify a team or organization with team_id
and org_id
using the route DELETE /organizations/:org_id/team/:team_id/discussions/:discussion_number/reactions/:reaction_id
.
Delete a reaction to a team discussion. OAuth access tokens require the write:discussion
scope.
octokit.reactions.deleteForTeamDiscussion({org,team_slug,discussion_number,reaction_id,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
Note: You can also specify a team or organization with team_id
and org_id
using the route DELETE /organizations/:org_id/team/:team_id/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id
.
Delete a reaction to a team discussion comment. OAuth access tokens require the write:discussion
scope.
octokit.reactions.deleteForTeamDiscussionComment({org,team_slug,discussion_number,comment_number,reaction_id,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
comment_number | yes | |
reaction_id | yes |
See also: GitHub Developer Guide documentation.
This method is deprecated.
Deprecation Notice: This endpoint route is deprecated and will be removed from the Reactions API. We recommend migrating your existing code to use the new delete reactions endpoints. For more information, see this blog post.
OAuth access tokens require the write:discussion
scope, when deleting a team discussion or team discussion comment.
octokit.reactions.deleteLegacy({reaction_id,});
name | required | description |
---|---|---|
reaction_id | yes |
See also: GitHub Developer Guide documentation.
List the reactions to a commit comment.
octokit.reactions.listForCommitComment({owner,repo,comment_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to a commit comment. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.
List the reactions to an issue.
octokit.reactions.listForIssue({owner,repo,issue_number,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
issue_number | yes | issue_number parameter |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to an issue. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.
List the reactions to an issue comment.
octokit.reactions.listForIssueComment({owner,repo,comment_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to an issue comment. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.
List the reactions to a pull request review comment.
octokit.reactions.listForPullRequestReviewComment({owner,repo,comment_id,});
name | required | description |
---|---|---|
owner | yes | |
repo | yes | |
comment_id | yes | comment_id parameter |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to a pull request review comment. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.
List the reactions to a team discussion comment. OAuth access tokens require the read:discussion
scope.
Note: You can also specify a team by org_id
and team_id
using the route GET /organizations/:org_id/team/:team_id/discussions/:discussion_number/comments/:comment_number/reactions
.
octokit.reactions.listForTeamDiscussionCommentInOrg({org,team_slug,discussion_number,comment_number,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
comment_number | yes | |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to a team discussion comment. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.
List the reactions to a team discussion. OAuth access tokens require the read:discussion
scope.
Note: You can also specify a team by org_id
and team_id
using the route GET /organizations/:org_id/team/:team_id/discussions/:discussion_number/reactions
.
octokit.reactions.listForTeamDiscussionInOrg({org,team_slug,discussion_number,});
name | required | description |
---|---|---|
org | yes | |
team_slug | yes | team_slug parameter |
discussion_number | yes | |
content | no | Returns a single reaction type. Omit this parameter to list all reactions to a team discussion. |
per_page | no | Results per page (max 100) |
page | no | Page number of the results to fetch. |
See also: GitHub Developer Guide documentation.