Use ncu and other existing tooling to manage maintainer/collaborator lists in README.md
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
It would probably make sense to add a workflow similar to https://github.com/nodejs/node/blob/HEAD/tools/lint-readme-lists.mjs / https://github.com/nodejs/node/blob/6909ea6db9ca56d25f7a24239e590ef667f6dea0/.github/workflows/linters.yml#L257-L285 to help keep the README in sync with the actual team
Originally posted by @aduh95 in https://github.com/nodejs/docker-node/issues/2455#issuecomment-4237542388
See also @nschonni's comment at https://github.com/nodejs/docker-node/pull/2455#issuecomment-4253888338 as he has started some experimentation on this.
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 by reading Node.js's referenced tools/lint-readme-lists.mjs and the linked .github/workflows/linters.yml section. Then inspect docker-node's README and existing workflows. Done means an automated workflow uses ncu or comparable tooling to keep maintainer and collaborator lists synchronized with the actual team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, node.js
- Domain
- ci-cd, documentation, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100