-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Proposal to map out outdated translations #1480
Comments
UlisesGascon
changed the title
Proposal for mark outdated translations
Proposal to map out outdated translations
Apr 2, 2024
Great idea! Keep in mind that the API doc is not translated, so this only applies to the rest of the doc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In our recent TC meeting, we discussed the need for a more efficient method of detecting outdated translated versions of our documentation. Below is a proposal aimed at addressing this issue and enhancing the user experience for our contributors.
Assumptions
Workflow
I propose creating a GitHub Action similar to the one discussed in Issue #1479. This action would detect changes made in any version using regex for the paths. It would then add tags in the PR for other versions that need translation, such as
needs fr translation
andneeds sp translation
. This tagging system would enable us to easily identify closed PRs requiring translation. For instance, we could filter closed PRs for the French version using a tag-based search: French Version PRs.If a change doesn't require translation, such as fixing a typo in the English text, we can simply remove the corresponding tags before merging the PR.
Next Steps
CONTRIBUTING.md
guide to incorporate this workflow.The text was updated successfully, but these errors were encountered: