Add up/downvotes to track usefulness of GH comments

[tedspare]

Maige, can you open a PR to tackle this issue? You could start with unit tests if desired.

• add a footer eg. "was this useful? vote up or down" to comments made by Maige
• assume we've added an event trigger for reactions. add an event listener for thumbs up/down reactions.
• store (answer, reaction) pairs in a new table called Feedback

[tedspare]

maige can you tackle this?

• fork or clone and branch the repo
• explore the codebase
• do research on the GitHub reactions webhook
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[ghost]

Hi @tedspare, I'm on it! I'll start by forking the repository, exploring the codebase, and researching the GitHub reactions webhook. Once I have a good understanding, I'll proceed with writing the code and opening a PR as instructed.

By Maige. How's my driving?

[tedspare]

maige can you tackle this?

• fork or clone and branch the repo
• explore the codebase
• do research on the GitHub reactions webhook
• make a plan
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[tedspare]

maige can you tackle this?

• fork or clone and branch the repo
• explore the codebase
• do research on the GitHub reactions webhook
• make a plan
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[tedspare]

ping

[tedspare]

maige can you tackle this?

• fork or clone and branch the repo
• explore the codebase
• do research on the GitHub reactions webhook
• make a plan
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[ghost]

I've reviewed the task and here is the plan of action:

1. Fork the RubricLab/maige repository (to be done through the GitHub website).
2. Explore the codebase to determine where to integrate the new feature.
3. Research GitHub reactions webhook to understand how to configure it for comment reaction events.
4. Add an event listener for issue_comment webhook events and handle reactions, specifically thumbs up (+1) and thumbs down (-1).
5. Implement Feedback storage by creating a Feedback table and storing (answer, reaction) pairs.
6. Modify the code to add a footer to comments with the message "Was this useful? Vote up or down."
7. Write unit tests for the new features.
8. Commit and push changes to the forked repository.
9. Open a Pull Request to the original repository for review.
10. Participate in the review process and make any necessary changes.

However, I am currently unable to clone the repository to start the implementation. If you could assist with this step, we can proceed with the development. Thank you.

By Maige. How's my driving?

[tedspare]

maige take a deep breath, you've got this:

• the repo is already cloned in your VM. make a new branch.
• explore the codebase
• do research on the GitHub reactions webhook
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[tedspare]

maige take a deep breath, you've got this:

• the repo is already cloned in your VM. make a new branch.
• explore the codebase. when in doubt, check what dir you're in.
• do research on the GitHub reactions webhook
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[tedspare]

maige take a deep breath, you've got this:

• the repo is already cloned in your VM. make a new branch.
• explore the codebase. when in doubt, check what dir you're in.
• do research on the GitHub reactions webhook
• write code
• add, commit and push changes
• open a PR
• don't worry about running the code, we'll take care of review

[tedspare]

maige can you tackle this?

one possible approach:

• clone the repo unless it's already cloned
• explore the code, check what dir you're in when in doubt
• write code
• add, commit, and push changes
• open a PR

be flexible, take a deep breath, you've got this

[tedspare]

maige can you tackle this?

one possible approach:

• clone the repo unless it's already cloned
• explore the code, check what dir you're in when in doubt
• write code
• add, commit, and push changes
• open a PR

be flexible, take a deep breath, you've got this