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
Is your feature request related to a problem? Please describe.
I have a need (in a corporate environment) for a global list of allow + deny list, but also the ability to add to the exclusion list on a per-repo basis.
Describe the solution you'd like
Two different approaches I can think of:
Allow passing --config multiple times and merge the configuration (order might matter here?)
Allow for passing --config but also look for <cwd>/deny.toml (and the other locations in pub fn get_config_path and do the config merge with the local key/values having precedence.
Changes to ValidConfig.load() would need to be made in either case.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I can put together a PR if this is functionality that would be accepted.
Thanks!
The text was updated successfully, but these errors were encountered:
Implement a solution for additional license exceptions configuration as
described in #541
Happy to entertain other solutions or approaches.
Minor typo fixed as well.
---------
Co-authored-by: Jake Shadle <jake.shadle@embark-studios.com>
Is your feature request related to a problem? Please describe.
I have a need (in a corporate environment) for a global list of allow + deny list, but also the ability to add to the exclusion list on a per-repo basis.
Describe the solution you'd like
Two different approaches I can think of:
Allow passing
--config
multiple times and merge the configuration (order might matter here?)Allow for passing
--config
but also look for<cwd>/deny.toml
(and the other locations inpub fn get_config_path
and do the config merge with the local key/values having precedence.Changes to
ValidConfig.load()
would need to be made in either case.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I can put together a PR if this is functionality that would be accepted.
Thanks!
The text was updated successfully, but these errors were encountered: