Skip to content

Conversation

@AshakaE
Copy link
Collaborator

@AshakaE AshakaE commented Jan 8, 2026

Added forced retranslation for wiki edits, initially once translated, the translated wikis remain the same except a forced retranslation occurs

Linked issues

closes https://github.com/EveripediaNetwork/issues/issues/4659

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @AshakaE, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the wiki update process by introducing forced retranslation for existing translated wikis. Previously, once a wiki was translated, subsequent updates to the original content would not automatically trigger a retranslation. This change ensures that translated versions in Korean and Chinese are kept up-to-date with the latest content modifications, improving consistency across languages. Additionally, it streamlines the codebase by removing an unused event capture mechanism.

Highlights

  • Forced Retranslation: Implemented a mechanism to force retranslation of wikis into Korean and Chinese upon updates, ensuring translated content remains current.
  • Updated translateWiki Method: The private translateWiki method now accepts an optional retranslate boolean parameter, which is passed to the underlying translation service to control forced retranslation.
  • Event Capture Removal: The captureEvent method, previously used for logging wiki creation/update events, has been removed along with its invocations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request enables forced retranslation of wikis upon updates by introducing a retranslate flag. The changes look good and achieve the goal. I've pointed out a bug in logging where the language is hardcoded, which could lead to confusing logs. Additionally, with the removal of the captureEvent method, the posthogService has become an unused dependency and should be removed for better code maintainability.

await this.revalidate.revalidatePage(wiki.id)
}
return true
}
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

With the removal of the captureEvent method, the posthogService is no longer used in this class. Please remove it from the class constructor and the corresponding import to keep the code clean and avoid injecting unused services.

} as unknown as Activity),
)

await this.captureEvent(
Copy link
Member

Choose a reason for hiding this comment

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

why remove all the posthog events?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it doesn't capture any event, it did post initially

@AshakaE AshakaE merged commit 0ce7db5 into main Jan 8, 2026
1 check passed
@AshakaE AshakaE deleted the retranslation branch January 8, 2026 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants