Workflow (GitHub) to check for translation errors
Open
Nobody has claimed this yet.
1. to develop
CI
developer experience
enhancement
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Follow up from https://github.com/nextcloud/server/pull/40825
Original comment from @szaimen
Makes sense. Could we somehow add a workflow that checks this? I saw this happening quite often in the past...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request #40825 and its referenced translation discussion, then inspect the repository's existing GitHub workflows for relevant conventions. The work is done when an automated workflow reliably detects translation errors; the issue does not specify particular files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, internationalization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100