Check for common problems when adding the "E-easy"/"E-less easy" labels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 281
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The first time the label is added, we should check for the presence of common issues. I need to think about what this involves, but off the top of my head:
- lack of filenames (a/b.rs), types/modules (a::b)
- lack of instructions involving mach (ie.
./mach test-wpt,./mach build-cef,./mach test-tidy)
We could leave a comment highlighting the missing pieces and linking to a document with best practices for filing issues intended for non-core contributors.
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
Start by locating the handling for the first addition of the "E-easy" and "E-less easy" labels, then review how comments and linked documentation are produced. Define which missing filenames, types or modules, and mach instructions should be detected; done means the checks reliably identify omissions and leave a useful comment pointing to best practices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100