Repository navigation
Transfer MattIPv4/discord-status-worker to nodejs org聽#960
Description
馃憢 I'd like to transfer https://github.com/MattIPv4/discord-status-worker into the nodejs org, please. It is a small Cloudflare Worker deployed to the nodejs.org account, providing a feed of the Node.js status page to the Node.js Discord server.
cc @nodejs/web-infra
Activity
AugustinMauroy commentedon Mar 25, 2025
is it already deployed to nodejs CF account ?
MattIPv4 commentedon Mar 25, 2025
Yes, this is already deployed (the repo has an Action setup to deploy
main), and is running in a channel in the Discord (albeit private at present).Trott commentedon Mar 27, 2025
@nodejs/tsc
ovflowd commentedon Mar 30, 2025
No. It is deployed to another account, also under Node.js, but it is not the build account. Why are you interested on knowing that? 馃憖
AugustinMauroy commentedon Mar 30, 2025
It surprised me that a repo is deployed when it's not in the org node can be published with the org account.
ovflowd commentedon Mar 30, 2025
I鈥檓 not sure why that would make a difference. The question is valid, but it depends on how these things are sourced, not on Cloudflare鈥檚 side. If the repository wasn鈥檛 ready for transfer, Matt and I wouldn鈥檛 have opened this request.
ovflowd commentedon Apr 7, 2025
cc @nodejs/tsc can we please do the transfer? 馃檹
legendecas commentedon Apr 7, 2025
+1
ovflowd commentedon Apr 14, 2025
@nodejs/tsc another bump :)
MattIPv4 commentedon Apr 21, 2025
馃憢 Hey folks, just wanted to check in on this and if there's anything I need to do to move this forward, as it's been open for close to a month now?
nschonni commentedon Apr 21, 2025
As this is a fork + patch/config of https://github.com/WalshyDev/cf-status-worker, could this also be achieved by adding scripts to the build repo instead?
MattIPv4 commentedon Apr 21, 2025
Yes, it probably could, though I'm hesitant to pollute the build repo with entirely new build scripts that'd be interfacing with Cloudflare workers, and something that'd be owned by web-infra rather than build?
nodejs/build#2299 (comment) also comes to mind when I previously tried to add net-new items to build and got nowhere.
nschonni commentedon Apr 21, 2025
Other idea would be to add a manual GitHub action in the node.js repo to clone + configure + push the original project
MattIPv4 commentedon Apr 21, 2025
Sure, you could have a manual GitHub Action, but it'd still need to store the patches + SHA somewhere, so it might as well be an automated one that does it based on pushes to said patches/SHA -- which is what the current repo I'm asking to transfer is, a home for said patches + SHA, and automated GitHub Actions to publish the worker when those are pushed.
Which repo are you referring to though, I'm not sure I see it fitting into build or nodejs.org?
flakey5 commentedon Apr 21, 2025
+1
aduh95 commentedon Apr 22, 2025
Here's what our policy says on repo transfer request approvals:
admin/GITHUB_ORG_MANAGEMENT_POLICY.md
Lines 64 to 67 in a51226f
The remaining action is to transfer the repo, which can only be done by the current repo owner, not the TSC.
MattIPv4 commentedon Apr 22, 2025
Ah wonderful, I wasn't aware such requests had auto-approval. Will start the transfer.
MattIPv4 commentedon Apr 22, 2025
Transferred over: https://github.com/nodejs/discord-status-worker. Would someone with the right powers grant web-infra permissions to the repo, either maintain or admin?
aduh95 commentedon Apr 22, 2025
I've added @nodejs/web-infra Maintain role, and remove the existing Write roles.