You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we just run unit tests on PR, then on merge to master we do full e2e tests. All via circleci.
With a goal of one day having a master branch that is always green/working.
We should look to having a workflow of PR (unit tests run) -> Review -> Merge to integration testing branch -> merge to master on success.
We can't run e2e tests on PRs due to ability to steal creds from circleci or steal resources from K8s clusters (e.g. bitcoin mining). So we need a manual review before public PRs can be automatically tested.
The text was updated successfully, but these errors were encountered:
Currently we just run unit tests on PR, then on merge to master we do full e2e tests. All via circleci.
With a goal of one day having a master branch that is always green/working.
We should look to having a workflow of PR (unit tests run) -> Review -> Merge to integration testing branch -> merge to master on success.
We can't run e2e tests on PRs due to ability to steal creds from circleci or steal resources from K8s clusters (e.g. bitcoin mining). So we need a manual review before public PRs can be automatically tested.
The text was updated successfully, but these errors were encountered: