Document translation workflow #2579
Open
Conversation
This file contains 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
mgeisler
force-pushed
the
document-translation-workflow
branch
from
9fde70e to
50828d1
Compare
| - Publish the entire `book/html/` directory to | ||
| https://google.github.io/comprehensive-rust/. | ||
|
|
||
| ### `build.sh` |
There was a problem hiding this comment.
I think we should mention when this script is being called (publish.yml and build.yml) and that both times there are artifacts that can be inspected if necessary.
| default to make it easier for people to run `mdbook build` without having to | ||
| configure LaTeX. | ||
|
|
||
| #### Restoring Translations |
There was a problem hiding this comment.
We should include that the English translation does not involve the git restore step and always builds from HEAD
|
This PR is relevant for #2541 |
michael-kerscher
requested changes
Apr 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a first draft of explaining the documentation workflow. Let's discuss this a bit before merging.