Jobbergate development workflow is the developer facing process by which jobbergate is developed.
There are two primary codebases that comprise the jobbergate project:
The development workflow for jobbergate-cli and jobbergate-api are fairly similar, but differ in a few ways also. Both jobbergate-api and jobbergate-cli use circleci to run tests and gate against code making it into master branch that doesn’t pass. The cicd for jobbergate-api will deploy the code in the pr to the jobbergate-api staging stack https://jobbergate-api-staging.omnivector.solutions (currently an internal/private endpoint at the time of writing).