Orphaned translations "by birth" should break in CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 233
- Forks
- 61
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
We have code that checks that the folder matches in the slug (in the front-matter).
But what if you create a brand new page, inside a translation, that doesn't exist in English (aka. github.com/mdn/content)
Then, it should break in CI.
E.g. cd translated-content && mkdir files/fr/web/nouveau && emacs files/fr/web/nouveau/index.html
It's possible that we're already checking this but it's worth checking this again.
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 locating the existing check for translation folders matching front-matter slugs and the CI workflow that runs it. Reproduce the case under files/fr/web/nouveau/index.html, then verify that CI rejects a translated page absent from github.com/mdn/content while accepting valid translations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100