Issues and pull requests / Issues
React to issues, pull requests and comments
You agree with an issue, or you want to say "I saw this", but a new comment adds noise and notifies each person who watches the thread. A reaction says it with one emoji, under the text.
3 min read
1. Add a reaction
- Open the issue or the pull request.
- Under its description, or under a comment, click the smiley button (Add reaction).
- Pick an emoji.
The emoji shows as a pill under the text, with a count. Your own pills look pressed.
You can pick from these 8 emoji:
| Emoji | Name |
|---|---|
| π | +1 |
| π | -1 |
| π | laugh |
| π | hooray |
| π | confused |
| β€οΈ | heart |
| π | rocket |
| π | eyes |
2. Add the same emoji, or take yours back
- To add an emoji that someone else used, click its pill.
- To take your reaction back, click your pressed pill again. You can also pick the same emoji again in the picker.
- Each person adds an emoji to a text one time. A second click takes it back.
3. See who reacted
Point to a pill. The tooltip names the people, for example "alice, bob, and 3 others reacted with hooray". The tooltip names up to 10 people.
Who can react
| Who | What they can do |
|---|---|
| People who can comment | Add and take back their own reactions |
| People who can only read | See the pills and the tooltips |
| On a locked conversation | Only people with write access react |
To lock a conversation, see Lock a heated conversation.
Some text has no reactions:
- A comment that screening holds, or that a maintainer hid, shows no reactions until it shows to everyone.
- A review with no text has no smiley button. A review with text has one, the same as a comment.
- A draft comment of your pending review has no smiley button.
Offline
On a repository without GitHub sync, a reaction works offline. It shows at once, and Source sends it when you are online again. See Work on issues offline.
On an item that syncs with GitHub, a reaction needs a connection. It goes to GitHub first. See Sync with GitHub.
Done
- An emoji shows under the issue, the pull request or the comment, with a count.
- Your own reactions look pressed, and a click takes one back.
- The tooltip of a pill names who reacted.
- The author gets one notification row for the item, with a count. See Get notified when someone needs you.
Later: src, REST and MCP
An agent confirms an item with a reaction, not with a comment. src has the same rules as the web:
src issue react 12 +1
src issue view 12 --json comments --jq '.comments[].id'
src issue react 12 eyes --comment 345
src issue react 12 +1 --remove
src issue react 12
- The emoji is a name from the table above, or its glyph (
π). The namesthumbsup,thumbsdown,tadaandsmilework too. --comment <id>reacts to a comment. Get the id fromsrc issue view <number> --json comments.--removetakes your reaction back.- With no emoji, the command lists the reactions: one line for each emoji, with the count and the names.
--json content,count,usersgives JSON. - For a pull request, use
src pr reactwith the same arguments.
REST and MCP:
| You want to | REST | MCP tool |
|---|---|---|
| List the reactions | GET .../issues/{n}/reactions | list_reactions |
| Add a reaction | POST .../issues/{n}/reactions, with { "content": "+1" } | add_reaction |
| Take a reaction back | DELETE .../issues/{n}/reactions/{content} | remove_reaction |
- The REST paths are under
/api/v1/repos/{owner}/{repo}. - For a comment, use
.../issues/comments/{id}/reactionsin REST, orcomment_idin MCP. - A name that is not in the table gets
400from REST, and an error from MCP andsrc.
Use the REST API and Connect over MCP have the details.