Hey no problem! Yeah I saw those checks and I think they are essentially
ignoring the types of warnings from pylint that my CI pipeline catches. I can't really ignore them globally because we want to conform to those standards in our codebase when writing code unrelated to metaflow.
I don't have a great sense for how pylint plugins work, was hoping there was a way to make pylint ignore specific warnings when for example a class is inheriting from
FlowSpec