-
Notifications
You must be signed in to change notification settings - Fork 152
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
[GH-500]: Fixed github issue "Emoji synchronisation for PR/issue on github" #632
Conversation
…#17) * test * Feat for adding reactions to comments * Fix checkstyle * revert readme * revert * [MI-2597]:Fixed github issue mattermost#500 for emoji synchronisation * [MI-2597]:Fixed review comments * [MI-2597]:Fixed review comments * [MI-2597]:Fixed review comments Co-authored-by: LokeshN <[email protected]>
Hello @Kshitij-Katiyar, Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. |
Thank you for the work @Kshitij-Katiyar ! Let me know what you think. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work 👍
server/plugin/plugin.go
Outdated
post, err := p.client.Post.GetPost(reaction.PostId) | ||
if err != nil { | ||
p.API.LogDebug("Error fetching post for reaction", "error", err.Error()) | ||
return orgRepo, id, objectType, false | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is costly. For most of the reactions posted, an RPC request is made to fetch the post. It's a bummer ReactionHasBeenAdded
doesn't provide the post.
Anyway, I don't see a way to get around the RPC call without changing the hook.
…n github plugin (#19) * [MI-2688]:Fixed review comments by mm team for issue mattermost#500 on github plugin * [MI-2688]:Fixed review comments * [MI-2688]:Fixed review comments
This PR has been automatically labelled "stale" because it hasn't had recent activity. |
@DHaussermann Gentle reminder to review the PR |
/update-branch |
We don't have permissions to update this PR, please contact the submitter to apply the update. |
@hanzei synced with master |
Thanks @Kshitij-Katiyar
Note I'm having an issue making the LGTM! |
Codecov ReportBase: 15.63% // Head: 15.53% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #632 +/- ##
==========================================
- Coverage 15.63% 15.53% -0.11%
==========================================
Files 15 15
Lines 5243 5414 +171
==========================================
+ Hits 820 841 +21
- Misses 4380 4530 +150
Partials 43 43
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
It looks like we don't take into account skin-tone emojis here. Maybe a good HW ticket to support this. More info here LokeshN#1 (comment) |
Summary
When the GitHub bot creates a post, it's always related to some specific issue/PR or comment. This PR has added the functionality that if a user reacts to the post in Mattermost with one of the 8 emojis supported for reactions on GitHub, the plugin will proxy this reaction to the appropriate PR/comment on GitHub. Likewise, if the user removes their emoji reaction in Mattermost, it will remove it in GitHub. The supported event notifications are:-
Issue/PR creations
Issue/PR comments
PR review comments
This PR is an extension of PR #575
Issue #500