Contributing
- Adding a new pipeline
- Code editor plugins
- Code formatting
- Contributing to an existing pipeline
- DSL2 Modules
- DSL2 Subworkflows
- Developer Tutorials
- Gitpod
- Graphic design guidelines
- Guidelines
- Pipeline Release Review Guidelines
- Release checklist
- Special content elements
- Synchronisation
- Test data guidelines
- Training material guide
Pipelines must have automated continuous integration testing, running using GitHub Actions.
There must also be CI tests using AWS (test and test_full).
There must be a config profile called test that should be as comprehensive as possible - that is, it should run as much of the pipeline as possible.
It should use as tiny test data set as possible (even if the output that it creates is meaningless).