stackabletech / stackabletech/stackablectl
Translation tooling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 4
Description
Ideally, we would have tooling to:
- Validate (in CI?) that all translation keys that are referenced have at least an english version
- Track completeness of other translations
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the translation keys and CI configuration, then determine how referenced keys and translation completeness are currently represented; done means both checks are defined and run as tooling or CI checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, localization, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100