Repository navigation
Request: read access to ci.nodejs.org for @semx #4468
Description
Activity
cc @MikeMcC399 — you helped me get nodejs/node#64449 through CI recently, so you've seen the context. Tagging you in case you can point me to the right person for read access here.
This was a recent policy change, documented in https://github.com/nodejs/node/blob/main/doc/contributing/pull-requests.md#continuous-integration-testing
See also #4355
Thanks @MikeMcC399 — that clears it up. I hadn't realized CI access was intentionally restricted to collaborators and platform teams now; the security-release rationale in #4355 makes sense. Appreciate the pointers to the docs. The GitHub Actions checks on the PR cover what I need for now, so I'll close this. Thanks again!
Reacted by Mike McCready
Hi @nodejs/build,
I regularly follow Node.js CI runs — most recently on my own PR nodejs/node#64449 (landed in
6b28d887), and more generally because my team works with Node.js and I often end up digging into CI/build questions for them.Logged in with my GitHub account (@semx), I get
Access Denied — semx is missing the Overall/Read permissionon ci.nodejs.org (for example on thenode-test-pull-requestjob pages), so I cannot see build progress or logs.Would it be possible to grant me read-only (Overall/Read) access, just to view build and test results? I am not asking to start or configure jobs.
Thanks!