nilslice
Considering a configuration file for protolock
Has a generic configuration file been considered for the tool (in addition to command line args)? It seems like a nice to have, especially for our workflow. We could have a similar setup prior to invoking protolock, but I'm happy to open a PR for a more generic solution if this aligns with the project's goals.
Hi @sidtaduri - thanks for this proposal. I don't have a strong opinion about the use of a configuration file, but I'd be interested to know what kind of things you'd like to include. It's worth mentioning @btc here, given their recent work on making protolock more configurable as well. @btc, if you have thoughts on this, please feel free to share.
@sidtaduri - if you don't mind, would you post an example configuration file that captures some of your thinking? Thanks!
