Hello, this is a super useful tool so firstly thanks for creating it!
After configuring the repos.yaml file I am however having issues.
In ~/.githubwatcher/repos.yaml:
`---
- caolan/nodeunit
- joyent/node`
However, I am getting notifications from caolan/node fork even though I am not actively watching it (on Github nor in the yaml configuration).
This also seems to cause an unresolved conflict between the joyent/node master and caolan/node fork. I am getting repeat Growl notifications about every 5 seconds. I've tried removing both repos from my yaml configuration, restarting the githubwatcher daemon, and eventually killing the githubwatcher daemon. Nothing seems to have stopped the repetitive notifications from these two repos. I've had to stop Growl in the interim until I can work out how to resolve this.
For example:
caolan/node
Has new -1058 forks
caolan/node
Was updated!
caolan/node
Has new -377 open issues
caolan/node
Has new -9142 watchers
joyent/node
Has new 1058 forks
joyent/node
Was updated!
joyent/node
Has new 377 open issues
joyent/node
Has new 9142 watchers
Perhaps the two repos are being compared given that caolan's fork of the joyent/node master gives the same values except they are negative for watchers, forks and open issues.
Any ideas? And for the repeat notifications after removal from the .yaml file, is this just a matter of kickstarting a process in order for githubwatcher to notice the configuration changes?
Hello, this is a super useful tool so firstly thanks for creating it!
After configuring the repos.yaml file I am however having issues.
In ~/.githubwatcher/repos.yaml:
`---
However, I am getting notifications from caolan/node fork even though I am not actively watching it (on Github nor in the yaml configuration).
This also seems to cause an unresolved conflict between the joyent/node master and caolan/node fork. I am getting repeat Growl notifications about every 5 seconds. I've tried removing both repos from my yaml configuration, restarting the githubwatcher daemon, and eventually killing the githubwatcher daemon. Nothing seems to have stopped the repetitive notifications from these two repos. I've had to stop Growl in the interim until I can work out how to resolve this.
For example:
caolan/node
Has new -1058 forks
caolan/node
Was updated!
caolan/node
Has new -377 open issues
caolan/node
Has new -9142 watchers
joyent/node
Has new 1058 forks
joyent/node
Was updated!
joyent/node
Has new 377 open issues
joyent/node
Has new 9142 watchers
Perhaps the two repos are being compared given that caolan's fork of the joyent/node master gives the same values except they are negative for watchers, forks and open issues.
Any ideas? And for the repeat notifications after removal from the .yaml file, is this just a matter of kickstarting a process in order for githubwatcher to notice the configuration changes?