For visibility - enabled public packages for the org
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
In support of https://github.com/nodejs/admin/issues/927 in order to support building a common wasm-builder image for dependencies.
I had to enable for members to be able to create public packages (they were already able to create private packages) - on this page - https://github.com/organizations/nodejs/settings/packages.
If there are any concerns with this please let me know
@nodejs/tsc
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
Read nodejs/admin#927 for the wasm-builder context, then review the organization package settings linked in this issue. Done means confirming whether public package creation is still intended for members and documenting any concerns or required follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100