merge "new-feature" & "enhancement" label
Open
Nobody has claimed this yet.
meta
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 1k
- Avg merge
- 1h 11m
- Merged PRs (30d)
- 4
Description
"new-feature" & "enhancement" labels serve the same functional purpose. "new-feature" is easily confused with the "new-module" label, so let's move all of these over to the default "enhancement" label.
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
Review the repository's current issue labels and identify every use of "new-feature" and "enhancement". Move the "new-feature" uses to "enhancement" and remove the redundant label; done means the labels no longer serve overlapping purposes and "new-module" remains distinct.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100