Skip to content
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

Turn off lookout by default - expect .lookout file per repo. #344

Closed
kuba-- opened this issue Nov 8, 2018 · 2 comments
Closed

Turn off lookout by default - expect .lookout file per repo. #344

kuba-- opened this issue Nov 8, 2018 · 2 comments
Labels
closed-duplicate This issue or pull request already exists enhancement New feature or request

Comments

@kuba--
Copy link

kuba-- commented Nov 8, 2018

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).

@dpordomingo dpordomingo added the enhancement New feature or request label Jan 11, 2019
@dpordomingo
Copy link
Contributor

dpordomingo commented Jan 11, 2019

@carlosms would the requested behavior be covered by source{d} Lookout Web-UI and GitHub Apps?
If so, could this issue be superseded by #403?

@dpordomingo dpordomingo added the help needed Further information is requested label Jan 11, 2019
@carlosms
Copy link
Contributor

Yes, I'd say #403 will cover this request, although not in the same way as described. Closing.

@dpordomingo dpordomingo added closed-duplicate This issue or pull request already exists and removed help needed Further information is requested labels Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants