Add automated documentation translation and publishing workflow - #3460
Open
Salvialf wants to merge 1 commit into
Open
Add automated documentation translation and publishing workflow#3460Salvialf wants to merge 1 commit into
Salvialf wants to merge 1 commit into
Conversation
Salvialf
added
the
changelog-docs
zoic21
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
.github/workflows/docs.yml: on push toreleasetouchingdocs/**, translatesdocs/fr_FRviajeedom/jeetranslate-docswhen it changed, and publishes tojeedom/documentationsviajeedom/workflows/docs-publish.ymlonce the translated locales (or images) actually land. Aworkflow_dispatchinput allows backfilling an already-shipped version from an arbitrary ref.Part of the documentation translation rework tracked in jeedom/documentations#166.
For context: #3252 explored a different direction for this same underlying problem (per-repo GitHub Pages hosting + browser-native translation). This PR is part of a different approach instead: keep
jeedom/documentationscentralized, with an automated DeepL-based translation pipeline replacing the broken one.The
publishjob is intentionally commented out in this PR.jeedom/documentationsstill has its old, duplicated layout onmaster; publishing now would write into it incorrectly. It must stay disabled until jeedom/documentations#166'sreworkbranch merges tomaster, and until theDOCS_REPO_TOKENorganization secret described there exists. Thetranslatejob is safe to enable right away, it never touchesjeedom/documentations.