Right now, I have it activated by default, but you have to set

[regex-lint].config

for it to work. The issue is that it causes this annoying output with

lint

✓ autoflake succeeded.
✓ isort succeeded.
- regex-lint skipped.

That is easily solved if you have to activate the backend instead

This isn't a problem with target-aware backends because they use

FieldSet.is_applicable()

in

core/goals/lint.py

to proactively determine whether the tool should run or not. I don't think that's feasible here because we need to access a subsystem to determine if

regex-lint

is activated or not, which requires using the Rules API. Compared to

FieldSet.is_applicable()

just using the Target API and plain-and-simple Python functions - no engine magic

Related, I have no idea where we should document this functionality. We never have really mentioned it bin docs before

Actually, maybe it's useful to let plugins distinguish between disabled vs skipped...? The idea of skipped is when you set

--black-skip

to temporarily skip. Or, maybe it's not actual that useful to render in the summary skipped? If we stop doing that, this problem is solved.

./pants --isort-skip fmt ::
✓ autoflake succeeded.
- isort skipped.

Here, we wouldn't show

isort

at all anymore. I think there's a minor risk that you set

[isort].skip = true

in

pants.toml

and don't realize why it's not running, but that fear is probably overblown...Thoughts?