-
-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support removing reactions #135
Comments
Hi @oxc I might be able to support this. What I'm thinking could work is to add a new input called I think the challenge with implementing this is going to be fetching the existing reactions and finding those that match the user of the I'm not going to be able to add this feature in quickly but I'll take a look when I have time. Thank you for suggesting it! In the meantime, you could attempt to remove reactions yourself by calling the API using github-script. |
Cool, thanks for your elaborate feedback! An alternative could of course be to just add a |
Would love to see this implemented as well. For our use, just replacing all reactions with a new set would be more than enough, no need for tracking who the reactions belong to. Would it be feasible to start with a "dumber" implementation like that first and then make it more sophisticated later on? Thank you for your efforts! |
Released the |
I would like to be able to remove reactions from a comment that I previously added.
Consider for example the following use case:
I have a long running job that results in a comment to PR.
When a new change is pushed, I want to indicate that I will update this comment by adding a reaction.
After the new comment content has been posted, I would like to remove this reaction again.
(This can of course as well be handled by adding text and replacing it later. If you want, I can think of a better use case 😂 )
The text was updated successfully, but these errors were encountered: