How do code linters that also automatically update the code fit into the pipeline steps?

[amfred]

See this comment: https://github.com/cdfoundation/sig-interoperability/pull/81/#discussion_r787764488

[bendory]

My 2c: this is not part of a CICD pipeline but rather part of code maintenance. Such a linter:

• is deployed as a gatekeeper, preventing merge into the main repo when issues are found, and suggesting (or automating) fixes prior to merge
• is deployed as an analyzer, automatically creating PRs (and possibly merging them) when issues are identified on existing code in the repo

The first use case is common for code formatting prior to commit or merge. The second use case is common for dependency management such as updating deprecated APIs to the latest version.