mary marchini

should we move the checklist from https://github.com/nodejs/admin/pull/484#issuecomment-604486043 to a new issue to make sure it doesn't get lost?

I suggested Johan open an issue here first to share more detailed context (and to let folks know this is being worked on), and then reference it on nodejs/admin. FWIW...

Not sure if there's anything that can be configured on Grafana (don't know if GitHub allows this level of granularity), but the OAuth requests read-only permission to all orgs it...

Any concerns on adding @nodejs/members with write permission? If we want to limit commits here, we could set branch restrictions.

I agree with @tniessen, and if the volume of undesired comments grows quickly, we can lock again and figure out another way to handle this.

@bnb we really should move the `nodejs-foundation` password to 1password 😅

We discussed that a bit on https://github.com/nodejs/admin/issues/618. If folks are concerned I can bring this up during a TSC meeting, but IMO we should just use the same account.

cc @nodejs/tsc @nodejs/community-committee needs two approvals from each committee

Wouldn't updating the `node-test-pull-request` be enough at least to fix the comment? This one seems more urgent (I'm reluctant of testing [auto start CI via labels](https://github.com/nodejs/node-auto-test/issues/15) because it will spam...

It's not commenting on node-auto-test, but it's also not commenting on nodejs/node. And when starting a CI on a PR from nodejs/node it still comments correctly. Not the best outcome,...