Repository navigation
Use ncu and other existing tooling to manage maintainer/collaborator lists in README.md #2463
Description
Activity
I flipped the people on "Docker Maintainers" to
maintaineron the team, but it has no affect on Mateo and Rafael, since they're org admins. I didn't remove myself from the maintainer role, but that's currently a diff.
Not sure if the NCU can be used to parse the role to have the different roles rather than new groups.I flipped the people on "Docker Maintainers" to
maintaineron the team, but it has no affect on Mateo and Rafael, since they're org admins. I didn't remove myself from the maintainer role, but that's currently a diff.Feel free to do a PR for yourself and I'll approve/merge it - as an active maintainer here it doesn't make sense for you not to be listed in there.
Not sure if the NCU can be used to parse the role to have the different roles rather than new groups.
If it can't at the moment that sounds like a useful enhancement we could look at making to it :-)
Not sure if the NCU can be used to parse the role to have the different roles rather than new groups.
I took a look at the documentation for ncu-team.md and it doesn't look like it displays a team member's role. Although automation would be nice to have, I'm not sure it's worth the effort given the small number of members & consolidation of the list into the one Markdown README file section only.
In any case, editing the lists is the easy part. The more difficult aspect is getting the affected parties to respond, and that requires human action!
Existing tools don't support this suggestion. Considering the low number of members and the low frequency of changes, I would suggest to drop the proposal. Manual management should be sufficient in this repo.
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 #2455 (comment)
See also @nschonni's comment at #2455 (comment) as he has started some experimentation on this.