This is a composite issue for creating new Pipeline Components request over the last few years: - [ ] Bats https://gitlab.com/pipeline-components/org/issues/-/issues/14 - [ ] djlint https://gitlab.com/pipeline-components/org/issues/-/issues/1 - [ ] golines https://gitlab.com/pipeline-components/org/issues/-/issues/2 - [ ] isort https://gitlab.com/pipeline-components/org/issues/-/issues/7 - [ ] Node https://gitlab.com/pipeline-components/org/issues/-/issues/5 - [ ] PlantUML https://gitlab.com/pipeline-components/org/issues/-/issues/15 - [ ] Pytest https://gitlab.com/pipeline-components/org/issues/-/issues/3 Before new components can be created, some other task need to be completed first. The most important of these are: - documenting the current workings of the automation behind the components - the release of the [Pipeline Components Linter][1] and the accompanying Pipeline Component [plc-lint][2] - Resolving the ARM/AMD container_scanning job failing [1]: https://gitlab.com/pipeline-components/org/pipeline-components-linter/ [2]: https://gitlab.com/pipeline-components/plc-lint