mary marchini

Maybe the bot lacks permission to comment on other repos?

The bot doesn't have write permission on that repo. I made a request to add it: https://github.com/nodejs/node-auto-test/issues/20

~In theory we need to ping TSC and CommComm, so that's a good start :)~ I might've mistaken the npm policy with repo creation policy 😅 I'm generally +1 if...

Misclicked while typing the comment above

@bnb I don't think we have any, but we could probably create one. Some ideas: - nodejs-contrib - nodejs-misc - nodejs-utils - nodejs-packages

ohh, I definitely misunderstood that before. In this case I'm -1 on using `@nodejs` as it can give the false impression for external users that the package is intended for...

OTOH other projects like Electron do publish tools intended for the project on `@electron` instead of a different scope: https://github.com/electron/build-tools

@wesleytodd by internal packages do you mean like shims for Node.js APIs (like readable-streams), or packages that are only relevant to the project (like node-core-utils)?

We have not used `llnode` jobs in years as we have been testing on Travis and then GitHub Actions. The intention was to test llnode on other Node.js supported platforms...

Can we disable it before removing? That way we can keep it disabled for a bit and if anyone scream we know it was being used. If no one screams...