Autofix: upgrade-nvm-tools

[autofix-bot]

Signed-off-by: Autofix autofix-bot@users.noreply.github.com

[jankeromnes]

This was me, as an experiment. If it's unhelpful I can turn it off.

Autofix is a tiny tool and service I built that regularly checks for known code defects (mostly small things like outdated version strings and trailing spaces) and can send Pull Requests automatically. It aims to propose small valuable fixes with no false positives to limit the burden on reviewers.

I'm just a bit unsure about the ECA, as a bot obviously can't sign it. Can I sign the ECA for the bot? Or should I send these automated PRs in my name? Any thoughts/ideas here are very welcome. I hope this can be useful (but again, it it's not, I'm happy to disable it).

[akosyakov]

@jankeromnes It would be good to propose it on dev meeting first.

BTW can such bots sign ECA if not i doubt we can merge it.

[jankeromnes]

@jankeromnes It would be good to propose it on dev meeting first.

Agreed, I'll add this topic to the next meeting's agenda.

BTW can such bots sign ECA if not i doubt we can merge it.

I think they can't, the ECA explicitly requests that you sign using your real name (no pseudonym, no anonymous contributions) so I guess bots are not allowed to sign.

[vince-fugnitto]

@jankeromnes It would be good to propose it on dev meeting first.

Agreed, I'll add this topic to the next meeting's agenda.

@jankeromnes maybe a compromise would be to create issues with 'help wanted' and 'good first issue' which will both track issues and attract new contributors?

[jankeromnes]

@jankeromnes maybe a compromise would be to create issues with 'help wanted' and 'good first issue' which will both track issues and attract new contributors?

I really like the idea to open issues tagged 'help wanted' or 'good first issue'! Thanks for the suggestion. The autofix bot can't yet automatically open issues, but maybe this can be implemented, or we could close automated Autofix PRs and manually reference them in new issues.

For now, I've grouped the current automated fixes in #7945, because at least the Node.js upgrade seemed important enough not to delay further.