Transfer MattIPv4/discord-status-worker to nodejs org

[MattIPv4]

👋 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

[AugustinMauroy]

is it already deployed to nodejs CF account ?

[MattIPv4]

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]

@nodejs/tsc

[ovflowd]

is it already deployed to nodejs CF account ?

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]

why are you interested on knowing that? 👀

It surprised me that a repo is deployed when it's not in the org node can be published with the org account.

[ovflowd]

why are you interested on knowing that? 👀

It surprised me that a repo is deployed when it's not in the org node can be published with the org account.

I’m not sure why that would make a difference. The question is valid, but it depends on how these things are sourced, not on Cloudflare’s side. If the repository wasn’t ready for transfer, Matt and I wouldn’t have opened this request.

[ovflowd]

cc @nodejs/tsc can we please do the transfer? 🙏

[legendecas]

+1

[ovflowd]

@nodejs/tsc another bump :)

[MattIPv4]

👋 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]

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]

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]

Other idea would be to add a manual GitHub action in the node.js repo to clone + configure + push the original project

[MattIPv4]

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?