-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
please advise if there is an active fork! #305
Comments
I’m happy to fork and apply the pending PRs here and in the other forks for a unified “Watcher3.1” - however my py3 skills are not great, it would be largely a PR-only repo with community support... |
That’s better than it being dead mate, the community will do its best to keep it alive, cheers.
Kind regards.
… On 6 Jul 2019, at 13:26, Barbeque Sauce ***@***.***> wrote:
I’m happy to fork and apply the pending PRs here and in the other forks for a unified “Watcher3.1” - however my py3 skills are not great, it would be largely a PR-only repo with community support...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
OK we're off to the races - https://github.com/barbequesauce/Watcher3 is up and running. You can switch your local instance over by doing Then confirm it's pointing to the right URL by issuing Hope this works for people... |
Thanks @barbequesauce, good work. I'll switch repos now. |
OK, I've switched repo here too, it was working for me but it will be easier to provide patches if I change something locally. I still hope that SmokingBandit would come back tho... |
Is anyone aware of an active fork of Watcher3? This one seems dead.
The PR's are piling up and issues are not responded to. Love this app but it's broken as-is and needs fixing.
The text was updated successfully, but these errors were encountered: