Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #941 +/- ##
==========================================
Coverage 74.42% 74.42%
Complexity 3116 3116
==========================================
Files 132 132
Lines 12179 12179
==========================================
Hits 9064 9064
Misses 3115 3115
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
ddadbf1 to
26531c1
Compare
…he title. Ensure if title translation fails, we don't update the title with an invalid value, like a blank string. Instead show an error notice
|
The E2E tests keep timing out on this PR. I bumped that timeout up a bit and can continue to bump that up if needed but seems like something else must be going wrong here. I ran these tests locally and they all pass fine so some additional investigation is needed |
|
I've tried both the previous 30-minute timeout and the new 35-minute timeout, and the tests seem to pass in both cases. I've kept the timeout at 35 minutes since we've come quite close to hitting the 30-minute mark in Actions on a few other PRs. Regarding the previous 35-minute timeout failure here, the checkout step itself took 6m 14s, whereas it normally completes in under 10 seconds. The run before that also seemed unusually slow overall, so this may have been an issue with the runner. The newly added test, in particular, passes consistently when run locally. |
What, Why, and How?
This PR adds a “Retry” action to the warning notice shown when a title or block translation fails.
For example, if 2 out of 10 blocks fail, the user can retry only those failed blocks instead of translating the entire post again. The PR tracks the client IDs of failed blocks and uses them to retry only the affected translations.
Use of AI Tools
AI assistance: Yes
Tool(s): Codex
Model(s): GPT-5.6 Sol
Used for: Code reviews and implementation suggestions.
Testing Instructions
Screencast
Retry.Generation.mov
Changelog Entry