Improve existing translations workflow #270
Description
Right now, translation notifications are sent on every change to main. This creates a lot of noise, and sometimes the template shows “new” or “removed” strings inaccurately, which makes it confusing for translators.
I'd like to propose a simple change to fix this.
Instead of sending notifications for individual changes on main, I suggest introducing a short-lived rc (release candidate) branch. When development for a version is finished, main would be merged into rc. At that point, strings are considered frozen.
Creating or updating the rc branch would be the single trigger for notifying translators (one notification per version). Translators would work only against rc, and once translations are done, rc can be merged back and released.
This has two clear benefits:
- Translators get notified exactly once, at the right moment.
- Everyone knows when a version is ready for translation, without noise from ongoing development.
No per-commit notifications, no inaccurate counts — just one clear signal when translations are actually needed.