Skip to content

meta: add automation policy#62871

Open
legendecas wants to merge 1 commit intonodejs:mainfrom
legendecas:automation-and-bots
Open

meta: add automation policy#62871
legendecas wants to merge 1 commit intonodejs:mainfrom
legendecas:automation-and-bots

Conversation

@legendecas
Copy link
Copy Markdown
Member

@legendecas legendecas commented Apr 21, 2026

Add an automation policy indicating that non-Node.js managed automation must seek approval or subject to immediate moderation.

Collaborators may use automation tools under their own names -- subject to CoC.

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

nodejs-github-bot commented Apr 21, 2026

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Apr 21, 2026
mcollina
mcollina approved these changes Apr 21, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mcollina mcollina added the fast-track PRs that do not need to wait for 72 hours to land. label Apr 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 21, 2026

Fast-track has been requested by @mcollina. Please 👍 to approve.

@tniessen
Copy link
Copy Markdown
Member

tniessen commented Apr 21, 2026

Nit: the commit message does not follow the commit message policy, and should probably be meta: add automation policy :-)

tniessen
tniessen reviewed Apr 21, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@tniessen tniessen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

English is not my first language, but to me, the first paragraph sounds like the automation tool or bot itself must be the one to open an issue before interacting with the project. That is probably not what is intended, and also at odds with the second paragraph.

@legendecas legendecas force-pushed the automation-and-bots branch 3 times, most recently from de5dc13 to 2474624 Compare April 21, 2026 15:08
@legendecas legendecas changed the title meta: automation policy meta: add automation policy Apr 21, 2026
@legendecas legendecas force-pushed the automation-and-bots branch from 2474624 to dfe0fee Compare April 21, 2026 15:10
@legendecas
Copy link
Copy Markdown
Member Author

legendecas commented Apr 21, 2026 •
edited
Loading

@tniessen I amended the wording clarifying that the automation owner should submit the request (or indicating who is the owner), and also subject to the moderation. Would you mind taking a look again? Thanks!

@legendecas legendecas added the meta Issues and PRs related to the general management of the project. label Apr 21, 2026
@panva
Copy link
Copy Markdown
Member

panva commented Apr 21, 2026 •
edited
Loading

Copilot may post automated project-uninvited PR reviews for a user who opted to it in their copilot settings. While not appreciated (by me at least) it is at least confined to the user's own PR.

@legendecas
Copy link
Copy Markdown
Member Author

legendecas commented Apr 21, 2026 •
edited
Loading

Copilot may post automated project-uninvited PR reviews for a user who opted to it in their copilot settings. While not appreciated (by me at least) it is at least confined to the user's own PR.

We can control and audit GitHub Copilot access at https://github.com/enterprises/nodejs/ai-controls/agents.

@legendecas legendecas added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 21, 2026
@aduh95
Copy link
Copy Markdown
Contributor

aduh95 commented Apr 21, 2026

Note that this does not exactly "adds" a policy, AFAICT it's always been the policy as defined in https://github.com/nodejs/admin/blob/43bc15c61b7fdc523016e60360419755c5dda79f/Moderation-Policy.md?plain=1#L178-L179

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tniessen tniessen tniessen left review comments

@mcollina mcollina mcollina approved these changes

@panva panva panva approved these changes

@jasnell jasnell jasnell approved these changes

@anonrig anonrig anonrig approved these changes

@targos targos targos approved these changes

@joyeecheung joyeecheung joyeecheung approved these changes

@richardlau richardlau richardlau approved these changes

@RafaelGSS RafaelGSS RafaelGSS approved these changes

@marco-ippolito marco-ippolito marco-ippolito approved these changes

@atlowChemi atlowChemi atlowChemi approved these changes

Assignees

No one assigned

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations. fast-track PRs that do not need to wait for 72 hours to land. meta Issues and PRs related to the general management of the project.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.