Skip to content

validation workflow for PRs that change translations #9751

@maribethb

Description

@maribethb

Check for duplicates

  • I have searched for similar issues before opening a new one.

Problem

we've had changes submitted to message files in the wrong format which can mess up the translatewiki sync and result in those changes being overwritten.

Request

Add a validation workflow that runs on every PR, and does checks to ensure that the only changes made to files in msg/json/*.json are ones that result from having made a change to msg/messages.js and then run npm run messages (which can update files as described here)

This workflow will catch instances where authors either incorrectly try to add a new localization token or we get PRs from folks trying to update translations instead of going through translatewiki

This workflow should not run against PRs from the translatewiki branch since that branch should have updates to the other messages files.

Alternatives considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue: feature requestDescribes a new feature and why it should be added

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions