Transfer Request: homebridge-teufel-raumfeld

[AlexPe-Code]

Plugin Name

homebridge-teufel-raumfeld

NPM Username

lexi500

Link To GitHub Repo

https://github.com/AlexPe-Code/homebridge-teufel-raumfeld

Do you plan to continue maintaining the plugin?

Yes - I will continue to maintain the plugin

Are you requesting a @homebridge-plugins/ scope for this plugin?

No - I am not requesting a @homebridge-plugins/ scope for this plugin

More Information

No response

[bwp91]

Hi @AlexPe-Code, thanks for wanting to transfer homebridge-teufel-raumfeld into the Homebridge organisation — and great that you'll continue maintaining it! 🙂

If you're happy to go ahead, there are two steps. Both transfer things to me (bwp91) first — that's just an intermediate step so that I can then personally move the repo and the npm package into the Homebridge plugins organisation on both GitHub and npm.

1. Transfer the GitHub repo to me (bwp91)

• Open your repo's Settings tab
• On the General page, scroll to the bottom ("Danger Zone")
• Click Transfer ownership → I understand, transfer this repository
• Under "New owner", enter bwp91 and confirm
• I'll accept the transfer and then move the repo into the organisation. Don't worry — you'll be added back as a collaborator so you can keep maintaining it

2. Add me as a maintainer on the npm package

Either on the npm website:

• Log in at npmjs.com and open the package page
• Go to the Admin tab → Invite maintainer
• Enter bwp91 and send the invite

Or from your terminal (logged in to npm):

npm owner add bwp91 homebridge-teufel-raumfeld

Once both are done, drop a comment here and we'll take it from there. Thanks!

[AlexPe-Code]

Hi [bwp91] all done , received an error when try to add you to npm.

[bwp91]

Hi @AlexPe-Code — good news: it all worked despite that error you saw. The repo is now in the Homebridge organisation, and I'm showing as a maintainer on npm too, so there's nothing left for you to do there. Thanks for sorting it so quickly! 🙂

One thing left to decide: how would you like new versions published to npm?

Option 1 — you keep publishing yourself. Nothing changes. You run npm publish from your machine, exactly as you do now.

Option 2 — I set up automatic publishing through GitHub. I add a workflow to the repo, and publishing then happens on GitHub instead of your machine. You'd never run npm publish again, and you wouldn't need an npm token locally.

It would work like this:

• A normal release — you bump the version in package.json (and package-lock.json), commit it, then create a GitHub release tagged vX.Y.Z. That publishes to npm as the normal version everyone installs.
• A beta version — you create a branch named beta-X.Y.Z (for example beta-0.4.0) and leave the version in package.json alone. Every commit you push to that branch publishes a beta automatically: the first is 0.4.0-beta.0, the next 0.4.0-beta.1, and so on. It's handy for getting a user to test a fix before it goes out to everyone.
• An alpha version — the same, but the branch is named alpha-X.Y.Z and it publishes under the alpha tag.

It also runs the linter before publishing, so a broken build can't reach npm.

This is the workflow we use on other plugins in the organisation, with the instructions written at the top of the file: https://github.com/homebridge-plugins/homebridge-tuya/blob/latest/.github/workflows/release.yml

Just let me know which you'd prefer. No rush!