search

scrutinizer-ci / scrutinizer

Legacy repository - archives past feature requests/bug reports
https://scrutinizer-ci.com/docs
140 stars 36 forks source link

Consider automatically assuming inherit: true in repository config #260

Open Bilge opened 10 years ago

Bilge commented 10 years ago

The build config for each repository allows specifying a "global config" in addition to a config for the repository. However, only the repository config takes effect. Settings in the global config are ignored.

schmittjoh commented 10 years ago

Did you add inherit: true to your repository config?

Bilge commented 10 years ago

I did not try that. Why should such a thing be necessary? If I select a global config cannot one assume that I'd like it to be applied without specifying an additional directive?

schmittjoh commented 10 years ago

I guess we could, on the other hand, we also require this if you'd like to inherit the repository/global config from a .scrutinizer.yml that is placed in your repository, so it's at least consistent.

Let's keep this issue open, so we can re-consider this behavior.

Bilge commented 10 years ago

:+1: Specifying inherit: true works for now.

patricknelson commented 8 years ago

Do you guys happen to have and solid documentation actually outlining this option? I'm finding .scrutinizer.yml configs with this option in it (inherit: true) but no sources as to what exactly it does, other than the implication that it inherits (and reading this here after some googling).

Is there a central point of documentation outlining all options? Because I'm not seeing that here, as it only mentions "main" sections (I'm worried about what other amazing and interesting options I may be missing): https://scrutinizer-ci.com/docs/configuration