WordPress / WordPress/wordpress-playground
Reuse nx-extensions between playground-tools and playground repos
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 462
- Avg merge
- 18h 44m
- Merged PRs (30d)
- 33
Description
packages/nx-extensions exists both in the playground-tools repo and the main wordpress-playground repo. Pull Requests such as https://github.com/WordPress/playground-tools/pull/110 modify one of them, creating a divergence and a likely a need for a backport at one point in the future. Let's find a single home for that code.
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
Compare packages/nx-extensions in the wordpress-playground repository with the corresponding package in playground-tools, starting with playground-tools PR #110. Determine which repository should be the single home and document the dependencies and migration impact. Done means the code has one maintained home and the duplicate does not diverge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100