Have CI generate .pot files and commit them

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Problem to solve

When someone changes a translate it often results into a pipeline failure for because the developer forgot to regenerate .pot files. I think this be easily automated.

Further details

For example:

  • https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8569
  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23218#note_118768164

Proposal

Always generate pot files and commit it if there is any change (probably cleanest way)

What does success look like, and how can we measure that?

Developers are not bugged anymore to have to regenerate the .pot files

Edited Sep 28, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading