Currently Feast CI is in a hybrid state. It has both GitHub Actions running linting and unit tests. At the same time any approved user (or code owner) will need to trigger a full range of tests through Prow in order to get there code merged in.
- Documentation should not require e2e tests
- Passive contributors should be able to see if quick and safe tests are passing before a contributor allows the full e2e suite to run. It shoud also not be a requirement that the full e2e suite run in order to merge code in.
Currently Feast CI is in a hybrid state. It has both GitHub Actions running linting and unit tests. At the same time any approved user (or code owner) will need to trigger a full range of tests through Prow in order to get there code merged in.