Clean out backlog of pull requests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
It doesn't look like there's a currently open issue for this, so:
Can something be done about the (as of writing) 553 currently open pull requests? A very large number either add features that have already been added, or can no longer be merged in without significant revisions. Clearing this backlog would make merging and organizing future PR's much easier.
I'll be flagging PR's that should be closed for attention, but I think that a maintainer of the website should go through the PR's to resolve this problem.
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 reviewing the repository's currently open pull requests and the issue's flagged candidates. Identify changes that duplicate existing features or require significant revisions, then coordinate with a website maintainer on closing or resolving them. Done means the backlog has been systematically reviewed and obsolete pull requests are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100