You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original idea was to have a lookout running per repo(s) by yourself. But over the time it turned on that lookout should be treated like CI services, etc.
If you have a lookout running by yourself it makes sense to have it turned on by default and you shouldn't have any extra config files.
But if we take a approach that lookout is a service running somewhere in the cloud (e.g. GCE) for all repos/orgs. then it should be turned off by default. In this case (to turn it on), you should be able to control it with config file. I believe having an extra .lookout file per repo is not a big deal (we already have a bunch of meta-files, like .travis.yml, appvoyer.yml so one more is not a big deal).
The text was updated successfully, but these errors were encountered:
Original idea was to have a lookout running per repo(s) by yourself. But over the time it turned on that lookout should be treated like CI services, etc.
If you have a lookout running by yourself it makes sense to have it turned on by default and you shouldn't have any extra config files.
But if we take a approach that lookout is a service running somewhere in the cloud (e.g. GCE) for all repos/orgs. then it should be turned off by default. In this case (to turn it on), you should be able to control it with config file. I believe having an extra .lookout file per repo is not a big deal (we already have a bunch of meta-files, like .travis.yml, appvoyer.yml so one more is not a big deal).
The text was updated successfully, but these errors were encountered: