Automattic / Automattic/gp-localci
Have leading/trailing whitespace trigger review comments
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Leading/trailing whitespace is either
- a typo
- an indication of translation concatenation
- design being implemented using whitespace
We should detect these and comment on them.
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 localization validation that produces review comments, then trace how message text is inspected and comments are created. Done means leading or trailing whitespace is detected and a review comment explains the issue for each affected message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- ci-cd, localization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100