Renovate: Add "ignore: true" option?

[rarkins]

Reading this article from @zephraph: http://artsy.github.io/blog/2018/11/26/keeping-dependencies-updated/

It got me thinking that we lean on "enabled": false quite a bit, especially in package rules. Would it be a good idea to introduce a little syntactic "sugar" of an "ignore": true option that means exactly the same as '"enabled": false`?

On one hand it can be "cluttering" to duplicate a config but on the other hand it's an important concept and can be better if the rules "read" more simply to users.

Thoughts, @hutson?

[Jamesking56]

Yeah I think it'll be good just as a kind of _negated alias_

[zephraph]

Having the single flag might be better for simplicity. Renovate already has a lot of features and that'd just be one more thing to document and one more difference between people's configs. With that said though this is pretty minor, and I don't feel strongly one way or another.

I think something that would be helpful is just having a set of small, concrete examples of how to do certain things. My blog post kind of shows how to only update packages in a certain namespace (while disabling everything else). Another example grouping things like all of react's dependencies into a single PR would be good. Just things like that so it's a little clearer to people how to acheive certain things. The docs are pretty good, but it'd just add another angle that people could look at it to understand things a little easier.

[rarkins]

Ok so maybe a little “cookbook” containing examples and also explaining why the example works, if it’s not obvious

[zephraph]

Yep! Once I understood that I had to create a package rule that ignored everything except the files that I wanted to update it was pretty straight forward. It just took a bit to fully see how everything pieced together.

[hutson]

On one hand it can be "cluttering" to duplicate a config but on the other hand it's an important concept and can be better if the rules "read" more simply to users. - @rarkins

Renovate already has a lot of features and that'd just be one more thing to document and one more difference between people's configs. - @zephraph

I agree pretty strongly with y'alls analysis here.

I, too, do not have a strong opinion one way or the other.

Ok so maybe a little “cookbook” containing examples - @rarkins

It seems a little tangential to the original question proposed in this issue, but I do agree that a _cookbook_ would be nice.

Many of the people I support for an on-premise instance of Renovate come to me with very broad problems, such as grouping all updates for a given package pattern to be filed on a given schedule.

We then spend time grep'ing Renovate documentation to collect all the individual options that, when put together, enable the desired workflow. It's difficult to know if certain options are meant to be used for our workflow, or whether our use of those options is _ideal_.