feat: post translation validation errors as a GitHub comment | FC-0012

[OmarIthawi]

Problem

Locating the validation error can be difficult in the GitHub Actions check.

Solution

Post a comment (e.g. #1894 (comment)) in the pull request with failed translations.

The comments are "sticky" to avoid spamming the pull requests with multiple comments.

Limitation: forks no supported

This won't affect us because bots writes directly to this repository.

Testing results

Testing results with screenshots

• Successful validation:
• Failed result:

References

This contribution is part of the FC-0012 project which is sparked by the Translation Infrastructure update OEP-58.

[openedx-webhooks]

Thanks for the pull request, @OmarIthawi! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[github-actions]

✅ All translation files are valid.

This comment has been posted by the validate-translation-files.yml GitHub Actions workflow.

[shadinaif]

neat! I like it. Thank you @OmarIthawi

[openedx-webhooks]

@OmarIthawi 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.