Splitting widget and app code about garminhomeassistant HOT 7 CLOSED

I think have two repos is the most clean and straight forwarded solution:

The widget code will be legacy code, which will only be changed for a bug fixing. It is unlikely, that it will be touch at all. And if it will be touch, even the commit history will be more cleaner because it will be dedicated.
It will make the app repo more clean, too. And it will be easier for all the tooling, to have separate repos.

I am not seeing any significant downsides for having two repos for this scenario. Or am I missing something here?

from garminhomeassistant.

New repo: https://github.com/house-of-abbey/GarminHomeAssistantWidget

Now we need to remove the irrelevant parts.

.. Joseph

from garminhomeassistant.

New repo: https://github.com/house-of-abbey/GarminHomeAssistantWidget
Now we need to remove the irrelevant parts.

I will do it for the Widget repo ✌️

Thank you. Happy to re-deploy a new version under the existing ID when you have completed the separation.

from garminhomeassistant.

@philipabbey What do you think? I could do the widget repo cleanup, because I can test it on my Venu.

from garminhomeassistant.

I was wondering if we had one Github repo with two source trees, which might confuse the tools, or two separate Github repos altogether?

from garminhomeassistant.

New repo: https://github.com/house-of-abbey/GarminHomeAssistantWidget

Now we need to remove the irrelevant parts.

I will do it for the Widget repo ✌️

from garminhomeassistant.

This issue will be continued for the rationalising of the application code.

from garminhomeassistant.