search

Teslemetry / homebridge

Homebridge integration for Teslemetry and Tessie
Apache License 2.0
1 stars 1 forks source link

Link update #1

Open TeslaOwnerTips opened 1 week ago

TeslaOwnerTips commented 1 week ago

Describe Your Problem:

I suggest updating the link in the image to point to git hub issues. It currently has a place holder link.

IMG_8495

Logs:

Show the Homebridge logs here, remove any sensitive information.

Plugin Config:

Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Bre77 commented 1 week ago

The Report An Issue button takes me to https://github.com/teslemetry/homebridge/issues Please update to the latest version (if not already) and check again.

TeslaOwnerTips commented 1 week ago

Still the same IMG_8506 IMG_8507

Bre77 commented 1 week ago

That looks like the correct link then, Teslemetry is building the Homebridge integration for both Teslemetry and Tessie, so that is the correct page. Where were you expecting it to take you?

TeslaOwnerTips commented 1 week ago

This is and will be confusing. I have never used a homebridge plugin that does not use a git hub repository with its own name to report bugs. So usually git hub link/developer/homebridge-tessie

The Read Me for above then has information similar to this https://www.npmjs.com/package/homebridge-tessie

Bre77 commented 1 week ago

I have an idea on how to address this, I'll ensure the home page goes to the right branch (which has the branded readme) and the new issue link goes to an appropriate issue template take makes it clear which service is being used.

I intend to keep using a single repo since over 95% of the code is identical between them, and so I can keep them both maintained in lockstep.

TeslaOwnerTips commented 1 week ago

I appreciate all your hard work.

TeslaOwnerTips commented 1 week ago

If I submit documentation pull requests that could be common to both branches do I submit them to the dev branch?

Most of the documentation will probably be the same with two options when it comes to specific platforms being used. This will reduce documentation overhead.

In the common documentation we could make it clear how to submit issues specific to the platform in use.

Do you want to start a wiki or do you want one large readme file?

Bre77 commented 1 week ago

I had not considered contributions yet. Documentation for both go to dev, and specific documentation goes to the respective branch. I'll take your PR and implement it.

TeslaOwnerTips commented 1 week ago

I’m not strong on github use so I’m not sure what to do with your edit. I didn’t see any approve/accept options. I just responded okay.