Fix Weblate POST validation issue

[whisper67265]

Summary by CodeRabbit

• Chores
  • Improved the translation workflow with enhanced error handling and response monitoring for the Weblate integration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 51dc9bbc-fe21-48b2-b8f1-8c4d50a45330

📥 Commits

Reviewing files that changed from the base of the PR and between bdfb682 and cbe6a88.

📒 Files selected for processing (1)

• .github/workflows/start-translation.yml

---

📝 Walkthrough

Walkthrough

The PR enhances the Weblate integration in the GitHub Actions workflow by replacing a fire-and-forget POST with a robust curl-based call that captures HTTP response codes, handles async (202) and sync (200) responses differently, and includes proper error handling and logging.

Changes

Weblate Integration Enhancement

Layer / File(s)	Summary
Documentation .github/workflows/start-translation.yml (line 231)	Comment clarified to reflect new asynchronous POST behavior: "async: server returns 202 + task_id quickly."
Core Implementation .github/workflows/start-translation.yml (lines 264–297)	Weblate POST refactored to use curl with response capture. HTTP 202 is logged as async success; HTTP 200 as sync success; unexpected codes trigger error output. Curl exit codes and HTTP responses are inspected before cleanup.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A rabbit hops through workflows bright,
Where Weblate calls now handle right—
No fire-and-forget, but responses caught,
202 and 200, each as it ought.
Async or sync, the logs now shine,
This workflow's more robust by design! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: improving Weblate POST validation by replacing a fire-and-forget approach with robust HTTP response handling and error detection.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}