Grant release team maintainer access to release-related tooling
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
#547 opened further questions about the structure of the Release WG. It has been discussed that release team should have some responsibility over release related tooling.
- Grant
@nodejs/releaserswrite access to release related tooling-
changelog-maker -
commit-stream -
branch-diff -
node-core-utils -
citgm
-
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
Review the unchecked checklist entries for commit-stream and node-core-utils, alongside the completed entries for changelog-maker, branch-diff, and citgm. Done means @nodejs/releasers has write access to the remaining release-related tooling and every checklist item is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100