Currently Published `nupm` Package is Not in `main` Branch
Open
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 335
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
I just noticed, that the currently published version of nupm, commit 84dfc5209593780ec98bda52e6c02a0a20d83f5b, is not part of the main branch.
I don't think that's to be expected.
Does it make sense to publish the current commit hash as a new version?
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 published commit 84dfc5209593780ec98bda52e6c02a0a20d83f5b with the main branch and review the package's release history. Confirm whether the published nupm version should correspond to main, then document the decision or update the published version so the release and branch are aligned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100