🌐 Sync German docs #14367
🌐 Sync German docs #14367
Conversation
Was forgotten in fastapi#14359. I already added it in fastapi#14367
|
@nilslindemann, sorry, I haven't reviewed and merged this in time and now it shows 1 outdated file ( Could you please update them and I will merge this PR |
|
Also, could you please help me understand whether I should merge #14368 before or after this? I think after, right? |
|
Hi @YuriiMotov, I think I made this and #14368, so that they do not interfere, but it is already a while ago, and I forgot XD. I should have made a note. I think you are right to first merge this, then the other. I created the translation for the new file
So the German translation is now in sync again. Greetings, Nils |
|
Sorry, but now it again shows me that at least two files modified by this PR are outdated:
|
|
I now think it's better to combine this PR with #14368. We can merge changes to docs from that PR to this PR and leave that PR with only changes to |
The LLM used that translation a lot ithis convinced me that "deployen" it is the better word. "bereitstellen" (or "ausliefern") is still used for "to serve".
|
@YuriiMotov Yes, there were a few more merges right after I synced it yesterday, holy moly, there is life in this repo. 😄 I have synced with the most recent changes again, and I have cherry-picked the commit from #14368 (which gave no merge conflict, so these PRs indeed did not interfere). Does the merging work now? For information, here is what I do before I bring my fork in sync with the FastAPI Repo: I check all merges which have been done, and for each merge which changes English Markdown documents, I create a "Sync with #xyz" commit and then make a PR. |
No description provided.