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

chore(ai-help): use private repo for internal feedback #9506

Merged
merged 1 commit into from
Aug 17, 2023

Conversation

caugner
Copy link
Contributor

@caugner caugner commented Aug 17, 2023

Summary

Problem

We already gather issue reports about AI Help answers from our users in a public repository, and now we would also like to collect internal feedback in the same way, but without mixing them with user reports.

Solution

Introduce an environment variable for the repository, and use a private repository for internal feedback on all nonprod builds.


How did you test this change?

Ran yarn && yarn dev with rumba running, opened http://localhost:3000/en-US/plus/ai-help/, clicked on "Report an issue with this answer on GitHub", and verified that it opens an issue in the private feedback repository.

To reduce noise on the public ai-feedback repo, we will
collect internal feedback in a private-ai-feedback repo.
@caugner caugner requested a review from LeoMcA August 17, 2023 10:22
@github-actions github-actions bot added plus work around features related to MDN Plus github-actions labels Aug 17, 2023
Copy link
Member

@LeoMcA LeoMcA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🚀

@caugner caugner merged commit 77585e7 into main Aug 17, 2023
15 checks passed
@caugner caugner deleted the use-private-ai-feedback-repo-for-nonprod branch August 17, 2023 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github-actions plus:ai-help plus work around features related to MDN Plus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants