Steve Manuel

Ah I missed re: the running on CI... The "commit" would be the responsibility of a user before pushing the code. How is the message removed from your codebase? Code-gen?...

> Where I want to move this discussion to is whether or not removing a message is considered a breaking change. If it is, then the rule should be changed...

> Removing a message without first deprecating all usages of it would simply not compile. That's a very good point, and something I tend to forget where `protolock` linting and...

@rost5000 - that sounds cool, thanks for sharing. I'm not sure how to publish to Maven repo though.. is this something that you could PR as a Github Action? I...

Thanks for the info, @rost5000 -- I have a few other things on my list with higher priority right now, but will get to this as soon as possible.

@wadejensen - thanks a lot for pointing this out! I will make the edit you've suggested. I'd be interested to see your Scala plugin if you're able to share!

Hey @viswajithiii - Before considering the PR you've suggested, would you be open to trying a comment annotation on your RPCs? Currently, the `@protolock:skip` hint will ignore a message from...

@viswajithiii - I wanted to follow up on this, since I am starting to think about supporting an optional configuration file for protolock. Within this conf, it would be possible...

@wadejensen, @viswajithiii - I will revisit this over the next few days and propose a config design/implementation. Will post back here with updates. Thanks!

@guyisra I suppose a minimal, extensible option would be to read a `--config` path and only support a single config option for the time being... ```yaml # protolock.yaml skip_rules: -...