Backporting changes from main to experimental
Open
Nobody has claimed this yet.
sustainment
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 2
Description
Pushing new updates from main to experimental
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 with pull request #351 and compare its changes with the experimental branch. Determine which changes from main still need to be applied to experimental, then verify that the branch is synchronized and its existing checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100