When updating multitools with a scheduled job as documented in https://github.com/bazel-contrib/rules_multitool/blob/main/docs/automation.md, it could happen that there are some tools that should not be updated as they should stay pinned to a particular version or contain some breaking changes that need to be fixed first. In this case, it would be great if there is a way to skip a particular tool from not being updated, for instance via a SKIP environment variable as used in https://pre-commit.com/#temporarily-disabling-hooks.
Example usage could look like SKIP=aws,ibazel multitool update which would update everything but aws and ibazel.
When updating multitools with a scheduled job as documented in https://github.com/bazel-contrib/rules_multitool/blob/main/docs/automation.md, it could happen that there are some tools that should not be updated as they should stay pinned to a particular version or contain some breaking changes that need to be fixed first. In this case, it would be great if there is a way to skip a particular tool from not being updated, for instance via a
SKIPenvironment variable as used in https://pre-commit.com/#temporarily-disabling-hooks.Example usage could look like
SKIP=aws,ibazel multitool updatewhich would update everything butawsandibazel.