Skip to content
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

AI Summary: emojis limited to 👍 and 👎 #7991

Closed
2 tasks
tianrunhe opened this issue Apr 4, 2023 · 5 comments
Closed
2 tasks

AI Summary: emojis limited to 👍 and 👎 #7991

tianrunhe opened this issue Apr 4, 2023 · 5 comments

Comments

@tianrunhe
Copy link
Contributor

Issue - Enhancement

To help us better understand how user like or dislike the AI summary, I think instead of providing the full emoji picker for the comment, we limit it to only 👍 and 👎. Furthermore, we put them along the header, sth like this:

Screenshot 2023-04-03 at 17 01 57

In the backend, we could still use the Reactji Interacted metric and simply just record +1 or -1.

This way it's much more streamline and easier to do analysis and would enable us to iterate our GPT models (e.g., A/B testing for different models).

Acceptance Criteria (optional)

  • User can vote 👍🏻 or 👎🏻 for AI comment
  • When a vote is cast, Reactji Interacted metric is sent to Segment, with value +1 or -1 respectively

Estimated effort: X points (see CONTRIBUTING.md)

@tianrunhe tianrunhe added this to the AI Summary milestone Apr 4, 2023
@tianrunhe tianrunhe changed the title AI Summary: emoji limited to 👍 and 👎 AI Summary: emojis limited to 👍 and 👎 Apr 4, 2023
@nickoferrall
Copy link
Contributor

Restricting emojis to only 👍 or 👎 would give us a slightly better understanding of whether users like the summaries, but it makes the UI a bit more busy/cluttered IMO. If we had our own custom model that we were training with user feedback, I think it would be worth doing.

But for gauging whether users want the summaries, I think we should focus on whether they toggle off the feature. We have a design issue (#7882) that's being worked on to add that functionality.

@github-project-automation github-project-automation bot moved this to To Prioritize in Sprint Board Beta Apr 11, 2023
@nickoferrall nickoferrall removed this from the AI Summary milestone Apr 17, 2023
@jordanh
Copy link
Contributor

jordanh commented Jul 7, 2023

I'd love to see the AC for this expanded slightly (or perhaps better or a follow-on issue added) that adds the option for the user to say why 👎 was pressed. I think it will help us optimize the engineering of these prompts better.

I think we got lucky when a user wrote in to support with bug #8491 ... it would be nice to catch other such cases more reliably

Copy link
Contributor

github-actions bot commented Jan 4, 2024

Stale issue

@github-actions github-actions bot added the stale label Jan 4, 2024
@tianrunhe tianrunhe removed the stale label Jan 4, 2024
@tianrunhe
Copy link
Contributor Author

I still want to do this, so removing the stale label. Might get to it as a side project some time.

@jordanh jordanh added the icebox label Mar 15, 2024
@jordanh
Copy link
Contributor

jordanh commented Mar 15, 2024

Iceboxing for now as I believe we need to focus on other things. @tianrunhe if you feel otherwise, please reopen

@jordanh jordanh closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: To Prioritize
Status: 🗄️Backlog
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants