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
We are using github webhook. And as far as I understand, only way to change some configuration is to create new elvis.config which consists "whole" config. What we would like to do is use the defautl one, with all the rules, and disable just one of them (or change options on it).
Coping default config is not something we would like to do. Mainly due to fact, that we could not easily see which options are project specific, and we could loose some new rules (one would have to keep track of all new rules, and update config accordingly).
Is there a way to just extend default config? Add/remove rules, or just override rule options?
If not it would be a great feature.
The text was updated successfully, but these errors were encountered:
mpmiszczyk
changed the title
Extending defaoult configuration.
Extending default configuration.
Oct 30, 2014
There's currently no way to extend the config file from the server when using Elvis as a webhook, but I think this is a nice feature to have. We'll give some thought on how this can be implemented and post the results here.
(Sorry for the late response, this issue went unnoticed up until now)
We are using github webhook. And as far as I understand, only way to change some configuration is to create new
elvis.config
which consists "whole" config. What we would like to do is use the defautl one, with all the rules, and disable just one of them (or change options on it).Coping default config is not something we would like to do. Mainly due to fact, that we could not easily see which options are project specific, and we could loose some new rules (one would have to keep track of all new rules, and update config accordingly).
Is there a way to just extend default config? Add/remove rules, or just override rule options?
If not it would be a great feature.
The text was updated successfully, but these errors were encountered: